Skip to content

Conversation

hugolefeuvre
Copy link
Contributor

This PR closes this PR : #782
Increase the version of Tooldistillator to 1.0.0+galaxy1. I am opening a new PR reusing the changes made by @clsiguret on the old one.
Thanks !

FOR CONTRIBUTOR:

  • I have read the Adding workflows guidelines
  • License permits unrestricted use (educational + commercial)
  • Please also take note of the reviewer guidelines below to facilitate a smooth review process.

FOR REVIEWERS:

  • .dockstore.yml: file is present and aligned with creator metadata in workflow. ORCID identifiers are strongly encouraged in creator metadata. The .dockstore.yml file is required to run tests
  • Workflow is sufficiently generic to be used with lab data and does not hardcode sample names, reference data and can be run without reading an accompanying tutorial.
  • In workflow: annotation field contains short description of what the workflow does. Should start with This workflow does/runs/performs … xyz … to generate/analyze/etc …
  • In workflow: workflow inputs and outputs have human readable names (spaces are fine, no underscore, dash only where spelling dictates it), no abbreviation unless it is generally understood. Altering input or output labels requires adjusting these labels in the the workflow-tests.yml file as well
  • In workflow: name field should be human readable (spaces are fine, no underscore, dash only where spelling dictates it), no abbreviation unless generally understood
  • Workflow folder: prefer dash (-) over underscore (_), prefer all lowercase. Folder becomes repository in iwc-workflows organization and is included in TRS id
  • Readme explains what workflow does, what are valid inputs and what outputs users can expect. If a tutorial or other resources exist they can be linked. If a similar workflow exists in IWC readme should explain differences with existing workflow and when one might prefer one workflow over another
  • Changelog contains appropriate entries
  • Large files (> 100 KB) are uploaded to zenodo and location urls are used in test file

Copy link

Test Results (powered by Planemo)

Test Summary

Test State Count
Total 1
Passed 0
Error 1
Failure 0
Skipped 0
Errored Tests
  • ❌ amr_gene_detection.ga_0

    Execution Problem:

    • Unexpected HTTP status code: 400: {"err_msg":"Workflow was not invoked; the following required tools are not installed: toolshed.g2.bx.psu.edu/repos/iuc/tooldistillator/tooldistillator/1.0.0+galaxy1 (version 1.0.0+galaxy1), toolshed.g2.bx.psu.edu/repos/iuc/tooldistillator_summarize/tooldistillator_summarize/1.0.0+galaxy1 (version 1.0.0+galaxy1)","err_code":0}
      

Copy link

Test Results (powered by Planemo)

Test Summary

Test State Count
Total 1
Passed 0
Error 1
Failure 0
Skipped 0
Errored Tests
  • ❌ amr_gene_detection.ga_0

    Execution Problem:

    • Failed to upload data, upload state is [error].
      

@hugolefeuvre
Copy link
Contributor Author

hugolefeuvre commented Aug 28, 2025

Error is the same (https://github.com/galaxyproject/iwc/actions/runs/17273630608/job/49024809466?pr=939#step:7:3383) as reported in the original PR with DB in cvmfs going wrong with empty SHA.
It has been solved by adding this galaxyproject/usegalaxy-playbook@5447308 for usegalaxy.org and it works. Do you think it's possible to re-use this in our case ?

@mvdbeek
Copy link
Member

mvdbeek commented Sep 1, 2025

Yes, can you open a PR to the tool that adds those environment variables ? Alternatively I think the container can be rebuilt with a newer git version.

@hugolefeuvre
Copy link
Contributor Author

hugolefeuvre commented Sep 8, 2025

Yes, can you open a PR to the tool that adds those environment variables ? Alternatively I think the container can be rebuilt with a newer git version.

Which method do you think is the best and most reusable/FAIR ?
I'm not sure I fully understand what you mean. Your first proposal is to make changes directly to the starAMR repository, and the second is simply to change the git version of the container ?

@mvdbeek
Copy link
Member

mvdbeek commented Sep 9, 2025

The easiest fix is this on line 37: https://github.com/galaxyproject/tools-iuc/blob/main/tools/staramr/staramr_search.xml#L37

export GIT_CONFIG_COUNT=1 GIT_CONFIG_KEY_0=safe.directory GIT_CONFIG_VALUE_0=* &&

You could also specify a minimum git version in the conda recipe that is the base for the container here: https://github.com/bioconda/bioconda-recipes/blob/master/recipes/staramr/meta.yaml#L36

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

Successfully merging this pull request may close these issues.

3 participants