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

fix: Remove incomplete marker for job finished only after metadata is written #3197

Merged
merged 2 commits into from
Nov 12, 2024

Conversation

fxwiegand
Copy link
Contributor

@fxwiegand fxwiegand commented Nov 12, 2024

This PR makes Snakemake remove the incomplete marker for a job thats finished only after the metadata is written. Otherwise the jobs starttime for the report was missing in the metadata and caused problems in the plot for the runtimes of individual jobs.

Summary by CodeRabbit

  • Bug Fixes

    • Adjusted the order of operations in the job completion process to ensure that incomplete markers are only removed after successful metadata recording, enhancing reliability.
  • Refactor

    • Improved the structure of the finished method for better clarity and maintainability while retaining existing functionality.

Copy link
Contributor

coderabbitai bot commented Nov 12, 2024

📝 Walkthrough

Walkthrough

The changes in this pull request primarily affect the finished method of the Persistence class in the snakemake/persistence.py file. The key modification is the repositioning of the _remove_incomplete_marker(job) function call, which is now executed after the job"s metadata has been recorded. This adjustment aims to ensure that the incomplete marker is only removed once the metadata storage process is confirmed to be successful. Overall, the structure and logic of the method remain unchanged.

Changes

File Change Summary
snakemake/persistence.py Repositioned the call to _remove_incomplete_marker(job) to occur after metadata recording in the finished method. No other significant changes to logic or structure.

Possibly related PRs


Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Generate unit testing code for this file.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai generate unit testing code for this file.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and generate unit testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot"s finite context window. It"s strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 0

🧹 Outside diff range and nitpick comments (1)
snakemake/persistence.py (1)

355-355: Consider adding error handling around metadata operations.

While the change fixes the immediate issue, consider these improvements:

  1. Wrap metadata operations in try-except to ensure incomplete marker is only removed if metadata is successfully written
  2. Consider making file operations async for better performance

Example implementation:

     async def finished(self, job):
         if not self.dag.workflow.execution_settings.keep_metadata:
             # do not store metadata if not requested
             return
+        try:
             code = self._code(job.rule)
             # ... existing code ...
             for f in job.output:
                 # ... existing code ...
                 self._record(
                     self._metadata_path,
                     {
                         # ... existing metadata ...
                     },
                     f,
                 )
+            self._remove_incomplete_marker(job)
+        except Exception as e:
+            logger.error(f"Failed to write metadata: {e}")
+            raise
-        self._remove_incomplete_marker(job)
📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Reviewing files that changed from the base of the PR and between 1be9935 and bcae57a.

📒 Files selected for processing (1)
  • snakemake/persistence.py (1 hunks)
🧰 Additional context used
📓 Path-based instructions (1)
snakemake/persistence.py (1)

Pattern **/*.py: Do not try to improve formatting.
Do not suggest type annotations for functions that are defined inside of functions or methods.
Do not suggest type annotation of the self argument of methods.
Do not suggest type annotation of the cls argument of classmethods.
Do not suggest return type annotation if a function or method does not contain a return statement.

🔇 Additional comments (1)
snakemake/persistence.py (1)

355-355: LGTM! This change fixes the metadata recording issue.

Moving the _remove_incomplete_marker call after metadata is written ensures that the job"s start time is properly preserved in the metadata. This is crucial for accurate runtime reporting in plots.

@johanneskoester johanneskoester merged commit 6567e5f into main Nov 12, 2024
36 of 37 checks passed
@johanneskoester johanneskoester deleted the job-times-missing branch November 12, 2024 11:46
johanneskoester added a commit that referenced this pull request Nov 21, 2024
Fix: This PR adds back the removal of the incomplete marker file also
when keep_metadata is False (i.e. --drop-metadata is active).

The removal calls were merged and put at the start of the function in
#3162, but this caused loss of starttime info in the metadata record. In
#3197 this was fixed, but by moving the removal call to the end of the
function, the incomplete tracker file was not removed anymore when
--drop-metadata was active. This PR adds the call to the removal
function back also for that case, and adds a note to inform why the code
is structured this way.

<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->
## Summary by CodeRabbit

- **Bug Fixes**
- Improved handling of job metadata by ensuring the incomplete marker is
removed only after successful metadata record creation, preserving job
start time.
  
- **Documentation**
- Added clarifying comments to explain changes regarding the incomplete
marker removal.
<!-- end of auto-generated comment: release notes by coderabbit.ai -->

---------

Co-authored-by: Johannes Köster <[email protected]>
johanneskoester pushed a commit that referenced this pull request Nov 27, 2024
🤖 I have created a release *beep* *boop*
---


##
[8.25.4](v8.25.3...v8.25.4)
(2024-11-27)


### Bug Fixes

* clean env vars in apptainer
([#3199](#3199))
([76d5329](76d5329))
* ensure that intermediate files in job groups do not cause spurious
mtime errors when checking for consistency with output files
([#3220](#3220))
([4ba2bdf](4ba2bdf))
* Remove incomplete marker also when drop-metadata is active
([#3215](#3215))
([a4f2e5c](a4f2e5c))
* Remove incomplete marker for job finished only after metadata is
written ([#3197](#3197))
([6567e5f](6567e5f))
* Support versioned URLs in Asset class and fix missing versions in
Snakemake report
([#3203](#3203))
([f086f6c](f086f6c))
* update rust-script usage to recent version (v0.35.0)
[#3183](#3183)
([#3208](#3208))
([43885d7](43885d7))


### Documentation

* clarify continuously updated input section
([#3219](#3219))
([72a6994](72a6994))
* Fix typo in CHANGELOG.md
([#3198](#3198))
([0e445ed](0e445ed))
* refer to Merkle trees instead of "blockchain" in caching.rst
([#3216](#3216))
([282e5d9](282e5d9))
* remove twitter in favor of bluesky and mastodon
([#3217](#3217))
([231c6df](231c6df))
* use "dictionary" not "array" wording in config docs
([#3156](#3156))
([17aed41](17aed41))

---
This PR was generated with [Release
Please](https://github.com/googleapis/release-please). See
[documentation](https://github.com/googleapis/release-please#release-please).

Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants