-
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
[24.1] Fix possible CircularDependencyError when importing collections #19017
base: release_24.1
Are you sure you want to change the base?
[24.1] Fix possible CircularDependencyError when importing collections #19017
Conversation
… only This avoids potential circular dependency errors.
To respect the view-only flag for copied_from_history_dataset_collection_association relationship.
I think e14d76a will fix these tests https://github.com/galaxyproject/galaxy/actions/runs/11380325900?pr=19017 But I'm not sure what will happen with this piece of code: galaxy/lib/galaxy/model/store/__init__.py Lines 1000 to 1011 in 1a6b7fe
Here we cannot associate directly using the id because those are new objects (their id is still None) and having the viewonly flag to true will ignore this assignment as far as I understand. |
307840a will fix this, but it feels "dirty" to commit in the middle of the import... so probably a bad idea? I am not sure how to work around it though... 😞 Update: nope, this early commit breaks then the HDA import with "HistoryDatasetAssociation without hid, this is not valid":
|
Fixes #18927
xref #19005
Making copied HistoryDatasetCollectionAssociation relationships view-only as an attempt to avoid potential circular dependency errors.
In practice, this gets rid of the error when importing but I'm not 100% sure this is the correct solution if
copied_from_history_dataset_collection_association
and/orcopied_to_history_dataset_collection_association
are meant to be used for persistency and not just for querying at any point.How to test the changes?
License