-
Notifications
You must be signed in to change notification settings - Fork 999
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 #19005
[24.1] Fix possible CircularDependencyError when importing collections #19005
Conversation
…nship view only This avoids potential circular dependency errors.
994787c
to
81ea92a
Compare
Nope, other tests will fail if set those relationships to view-only. Out of ideas then... @jdavcs do you know how to get rid of the circular dependency here? |
Which tests are that ? |
At least these 2:
|
I would ignore the unit test, that's fairly artificial. Do you have a link to the CI results ? |
Here from the API tests: https://github.com/galaxyproject/galaxy/actions/runs/11364836955 |
https://github.com/galaxyproject/galaxy/actions/runs/11364836955/job/31611696527#step:10:1167:
this might be good and I wouldn't necessarily say you're on the wrong track ? |
Alright, I'll reopen and investigate the test. Update: GitHub doesn't let me reopen it because I force-pushed it while it was closed. I'll have to open a new one. |
Fixes #18927
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