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

Workflow : Input fasta.gz (as fasta) not actually using the decompressed file #19771

Open
Delphine-L opened this issue Mar 7, 2025 · 2 comments

Comments

@Delphine-L
Copy link
Contributor

Describe the bug
I am running a workflow that needs a fasta as an input. On the workflow run form, the input show "Dataset X (as fasta)" but the tool connected to the input run on the compressed file (this tool accepts both fasta and fasta.gz but fails on compressed files. I am working on these failures separately).

Galaxy Version and/or server at which you observed the bug
Galaxy Version:{"version_major":"24.2","version_minor":"1.dev0"}

Browser and Operating System
Operating System: macOS
Browser: Chrome

To Reproduce
Steps to reproduce the behavior:

  1. Import history https://usegalaxy.org/u/delphinel/h/test-implicit-compression
  2. Import workflow https://vgp.usegalaxy.org/u/delphinel/w/test-dustmasker
  3. run workflow on dataset 1
  4. See that the dataset appears as "1: GZIP compression on data 1 (as fasta)"
  5. The Dustmasker step will fail ( see dataset 2 : invocation )
  6. Click on information. See that it ran on the compressed file, not on a hidden result of an implicit decompression step.

Expected behavior
The compressed file should be implicitly uncompressed before running the tool (As it has been the case for dataset 3 where the input is dataset 1 uncompressed).

@mvdbeek
Copy link
Member

mvdbeek commented Mar 7, 2025

I don't think we will fix this, workflow inputs are either compatible or they are not, and once the step input has been recorded ... that's it. We'd basically be building up something to work around broken tools, and given the constraints and the likely not straightforward fix it is probably not worth doing.

@Delphine-L
Copy link
Contributor Author

If it's not going to be decompressed, can we at least prevent it from saying "as fasta" ?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants