-
Notifications
You must be signed in to change notification settings - Fork 1k
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 Collection as input #18927
Comments
@patrick-austin do you have the entire stacktrace? Thanks for the detailed description! |
After some more experimentation it looks like this might only be a problem when using the "Send results to a new history" option. Maybe there's a problem in how the metadata is formatted at export/import time for collections that are sent to a new history? For a "real" example we had, not sending to new history resulted in an RO-Crate that could be re-imported. But for the example I gave above it seems to fail with a different error, this time (see bottom). An even more simple example that doesn't even run a tool does work though: Invocation without sending to new history (should work): Invocaion with sending to new history (doesn't work for me): Apologies for not including the full stack for the original error, it seemed to be a lot of SQLAlchemy rolling back for the same underlying error but perhaps there is something useful in there:
As for trying to do a dataset extraction, re-importing the invocation, e.g.: fails with a different error:
|
It should be fixed in #19215, thank you! |
Describe the bug
When attempting to import an exported RO-Crate for a Workflow Invocation that uses a Dataset List Collection as input, an error is returned to the UI:
History import failed.
Galaxy Version and/or server at which you observed the bug
Galaxy Version: 24.1.1
Commit: 940a87c8bf248c0d1cecd61b2e19fd37ce097777
Also tried on usegalaxy.eu and got the same error.
Also tried on 23.2, and the import did not succeed but also did not error (job stays running indefinitely).
Browser and Operating System
Operating System: Windows
Browser: Firefox
To Reproduce
Steps to reproduce the behavior:
Invocation-of-Input-Dataset-Collection-Test-at-2024-10-02T170508077452.rocrate.zip
Since this will fail, I also provide the simplest example workflow I could think of (used in the above):
Galaxy-Workflow-Input_Dataset_Collection_Test.txt
This should be a
.ga
but had to rename to.txt
to allow upload to GitHub.Expected behavior
Import to succeed.
Screenshot
Additional context
Ultimately, the error seems to be:
We found this in our log files, wrapped in a SQLAlchemy rollback error. I don't have the knowledge of Galaxy server to dig any further into the cause, but we did a lot of trial and error on our instance and the presence of the Collection as input seemed to be the common link, and is referenced in the error message above.
The text was updated successfully, but these errors were encountered: