[23.0] Fix output datatype when uncompressing a dataset with incorrect datatype #17944
Conversation
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
with the ``CONVERTER_gz_to_uncompressed`` tool. Previously, if a user forced an incorrect datatype to a compressed input dataset (e.g. `fastqsanger` instead of `fastqsanger.gz`), then the output datatype assigned by this tool would be an invalid one (`fastqsan`). Fix galaxyproject#17938.
|
Thanks a lot @nsoranzo! |
nsoranzo
changed the title
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.
with the
CONVERTER_gz_to_uncompressedtool.Previously, if a user forced an incorrect datatype to a compressed input dataset (e.g.
fastqsangerinstead offastqsanger.gz), then the output datatype assigned by this tool would be an invalid one (fastqsan).Fix #17938.
How to test the changes?
(Select all options that apply)
License