[25.0] Propagate cached job output replacement to copies of outputs #20553
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
github-actions
bot
added
the
area/database
mvdbeek
force-pushed
the
live_fix_cry_emoji
branch
from
870e7f6 to
d613247
Compare
…peration tools) Should fix the issue we had during Galaxy live, where we had a step in which we picked the first dataset collection element from a mapped over collection whose outputs where not yet replaced by the job cache. The effect of this is that the extracted dataset's dataset was deleted, and all downstream jobs where waiting for this dataset to become terminal.
mvdbeek
force-pushed
the
live_fix_cry_emoji
branch
from
a72048c to
b691b93
Compare
github-actions
bot
changed the title
mvdbeek
changed the title
|
Very sorry I let this slip through the cracks. Thanks for the fix. |
This was referenced Aug 1, 2025
Closed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Such as those made by Database Operation or expression tools.
Should fix the issue we had during Galaxy live, where we had a step in which we picked the first dataset collection element from a mapped over collection whose outputs where not yet replaced by the job cache.
The effect of this is that the extracted dataset's dataset was deleted, and all downstream jobs where waiting for this dataset to become terminal.
How to test the changes?
(Select all options that apply)
License