Closed bgruening closed 1 year ago
Interesting if I disable metadata_strategy: extended
, so I assume it takes the default, it is working as expected.
Its a bit hard to debug as the tool only generates one collection and this is empty so there is no stderr/stdout attached.
Did you check the job in the database ? The traceback might be attached there, and the UI is just missing a link the to component (https://github.com/galaxyproject/galaxy/issues/14980)
only generates one collection
I think the tool generates no collection ? https://github.com/galaxyproject/tools-iuc/blob/master/tool_collections/bamtools/bamtools_split/bamtools_split.xml#L46 ... but you should have a hidden dataset in the history if the discovery fails.
Fix is in https://github.com/galaxyproject/galaxy/pull/15038
It is this tool https://github.com/galaxyproject/tools-iuc/blob/master/tool_collections/bamtools/bamtools_split/bamtools_split_ref.xml#L42
Failed collection:
Correct collection without extended metadata:
Thanks for the quick fix will try it now ...
The tool
Split BAM by Reference into dataset list collection
https://usegalaxy.eu/root?tool_id=toolshed.g2.bx.psu.edu/repos/iuc/bamtools_split_ref/bamtools_split_ref/2.5.1+galaxy0 generates the following stack trace on EU.Its a bit hard to debug as the tool only generates one collection and this is empty so there is no stderr/stdout attached. However, looking at the JWD the results do exist.
EU is running celery and
metadata_strategy: extended