-
Notifications
You must be signed in to change notification settings - Fork 1k
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
[24.0] Do not copy purged outputs to object store #18342
Merged
mvdbeek
merged 16 commits into
galaxyproject:release_24.0
from
mvdbeek:fix_copying_purged_files
Jun 11, 2024
Merged
Changes from all commits
Commits
Show all changes
16 commits
Select commit
Hold shift + click to select a range
87124a3
Don't copy from_work_dir outputs to purged path in shell fragment
mvdbeek c3a5d61
Don't include purged outputs in from_work_dir outputs
mvdbeek a1d41ab
Raise appropriate exception if require path parameter is missing
mvdbeek 8e6e25d
Don't push purged dataset contents to object store
mvdbeek 8bc3f21
Add tool that produces all types of outputs
mvdbeek 65e9605
Don't fail _finish_or_resubmit if tool_stdout / tool_stderr not written
mvdbeek 435a8cd
Fix up test cases
mvdbeek 03eca7c
Fix handling of collecting discovered but purged outputs
mvdbeek eb2e318
Elevate external metadata setting to warning
mvdbeek fc42b61
Fix metadata setting on purged outputs
mvdbeek a35033d
Extend test to make sure disk path remains purged
mvdbeek c489eb2
Set file_size and total_size to 0 for discovered but purged datasets
mvdbeek 5ab3120
Purge dataset if finishing job for purged output
mvdbeek 50b7f8f
Do not overwrite purged or deleted states when importing datasets fro…
mvdbeek 3c7730c
Delete purged outputs from object store when importing dataset for pu…
mvdbeek f0e09cc
Fix up tests
mvdbeek File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains 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
This file contains 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
This file contains 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
This file contains 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
This file contains 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
This file contains 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
This file contains 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
This file contains 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
This file contains 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
This file contains 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
This file contains 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
This file contains 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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,90 @@ | ||
<tool id="all_output_types" name="all_output_types" version="1.0.0" profile="24.0"> | ||
<command><![CDATA[ | ||
sleep $sleep_param && | ||
echo hi > output.txt && | ||
echo hi > '$static_output' && | ||
echo hi > '$static_output_2' && | ||
cp '$c1' galaxy.json | ||
]]> | ||
</command> | ||
<configfiles> | ||
<configfile name="c1">{"output_tool_supplied_metadata": { | ||
"name": "my dynamic name", | ||
"ext": "txt", | ||
"info": "my dynamic info" | ||
}} | ||
</configfile> | ||
</configfiles> | ||
<inputs> | ||
<param name="sleep_param" type="integer" value="0" /> | ||
</inputs> | ||
<outputs> | ||
<data name="static_output" format="txt" /> | ||
<data name="static_output_2" format="txt" /> | ||
<data name="output_workdir" from_work_dir="output.txt" format="txt" /> | ||
<data name="output_tool_supplied_metadata" from_work_dir="output.txt" format="auto" /> | ||
<data format="txt" name="discovered_output"> | ||
<discover_datasets pattern="(?P<designation>.+)\.txt" ext="txt" visible="true"/> | ||
</data> | ||
<data format="txt" name="discovered_output_replaced"> | ||
<discover_datasets pattern="(?P<designation>.+)\.txt" ext="txt" visible="true" assign_primary_output="true" /> | ||
</data> | ||
<collection type="paired" name="static_pair" format="txt"> | ||
<data name="forward" from_work_dir="output.txt"></data> | ||
<data name="reverse" from_work_dir="output.txt"></data> | ||
</collection> | ||
<collection type="list" name="discovered_list" format="txt"> | ||
<discover_datasets pattern="(?P<designation>.+)\.txt" ext="txt" visible="true" /> | ||
</collection> | ||
</outputs> | ||
<tests> | ||
<test> | ||
<output name="static_output"> | ||
<assert_contents> | ||
<has_text text="hi"/> | ||
</assert_contents> | ||
</output> | ||
<output name="output_workdir"> | ||
<assert_contents> | ||
<has_text text="hi"/> | ||
</assert_contents> | ||
</output> | ||
<output name="output_tool_supplied_metadata"> | ||
<assert_contents> | ||
<has_text text="hi"/> | ||
</assert_contents> | ||
</output> | ||
<output name="discovered_output"> | ||
<discovered_dataset designation="output" ftype="txt"> | ||
<assert_contents> | ||
<has_text text="hi"/> | ||
</assert_contents> | ||
</discovered_dataset> | ||
</output> | ||
<output name="discovered_output_replaced" count="1"> | ||
<assert_contents> | ||
<has_text text="hi"/> | ||
</assert_contents> | ||
</output> | ||
<output_collection name="static_pair" type="paired"> | ||
<element name="forward" ftype="txt"> | ||
<assert_contents> | ||
<has_text text="hi"></has_text> | ||
</assert_contents> | ||
</element> | ||
<element name="reverse" ftype="txt"> | ||
<assert_contents> | ||
<has_text text="hi"></has_text> | ||
</assert_contents> | ||
</element> | ||
</output_collection> | ||
<output_collection name="discovered_list"> | ||
<element name="output" ftype="txt"> | ||
<assert_contents> | ||
<has_text text="hi"></has_text> | ||
</assert_contents> | ||
</element> | ||
</output_collection> | ||
</test> | ||
</tests> | ||
</tool> |
Oops, something went wrong.
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This seems to be a wild check 😭. I hate it but I don't know the alternative. I know people love the disk object store and jobs writing directly to the object store 🤔.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It's a bit of an "optimization" .. I'm happy to restore the original version, the important thing is that we don't store data in purged datasets.