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

Cannot import RO-Crate of an Invocation using hidden outputs #18995

Closed
patrick-austin opened this issue Oct 15, 2024 · 0 comments · Fixed by galaxyproject/gxformat2#106
Closed

Comments

@patrick-austin
Copy link
Contributor

Describe the bug
Importing an RO-Crate for a Workflow Invocation changes action_arguments from {} to true. This leads to

Workflow cannot be executed. Please resolve the following issue:
Uncaught exception in exposed API method: 

When attempting to run the re-imported workflow.

Galaxy Version and/or server at which you observed the bug
Galaxy Version: 24.1.2
Commit: 04abcd5b342a5ed1f5ac2a3c1836a18deb929fac

Also observed on materials.usegalaxy.eu (24.1.2dev0).

Browser and Operating System
Operating System: Windows
Browser: Firefox

To Reproduce
Steps to reproduce the behavior:

  1. Create a workflow and hide one of the outputs
  2. Run the workflow
  3. Export the invocation
  4. Import the invocation
  5. Try to run the re-imported workflow
  6. Workflow cannot be executed. Please resolve the following issue:
    Uncaught exception in exposed API method:

Expected behavior
Workflow runs, and contents of the .ga for the workflow is unchanged.

Screenshots
image

Original workflow via .ga download:
Galaxy-Workflow-Original.txt

RO-Crate export (action_arguments is still {} in the zipped .ga file):
Invocation-of-Unnamed-Workflow-at-2024-10-15T091729087732.rocrate.zip

Re-imported workflow (action_arguments is now true), via .ga download:
Galaxy-Workflow-ReImported.txt

Additional context
Possibly related to #18927 , as it also seems like it could be a problem with workflow metadata being re-imported via the invocation RO-Crate.

@mvdbeek mvdbeek self-assigned this Oct 15, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants