Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Provenance tracking, detecting errors #107

Open
rvosa opened this issue May 2, 2024 · 0 comments
Open

Provenance tracking, detecting errors #107

rvosa opened this issue May 2, 2024 · 0 comments
Assignees

Comments

@rvosa
Copy link
Member

rvosa commented May 2, 2024

SnakeMake's ability to generate provenance reports and detect errors is fairly limited. When failures happen, intimate knowledge of the pipeline is needed to understand what may be going on. Any enhancements that could improve this are very welcome. One thing to address in particular is to devise a more standardized logging policy. Currently, the Python logging module is used. However, it is applied somewhat haphazardly and results in many log files (e.g. one for each parallel instance of a rule). In addition, some rules invoke command line programs directly, redirecting STDERR to a log. Better would be if logging was consistently applied, failures were trapped, and the log files could be reliably interrogated to track where errors happen.

This issue is considered 'done' when actionable instructions exist for detecting errors in the logging system for users.

@rvosa rvosa self-assigned this May 30, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: In progress
Development

No branches or pull requests

1 participant