[19.09] Fix DetachedInstanceError when tool shed packages are in play #8933
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Should this target 19.09? |
blankenberg
approved these changes
Nov 5, 2019
mvdbeek
changed the title
jmchilton
merged commit 9aec180
into
galaxyproject:release_19.09
10 checks passed
|
Hi, I got the same error message ( Parent instance <ToolShedRepository at 0x7f339f9b9a10> is not bound to a Session; deferred load operation of attribute 'metadata' cannot proceed ), but I am still in Galaxy 19.09. May you help on this ? |
|
@nagoue This issue has been fixed and backported to 19.09 in #9354. If you still get this kind of error, please open a new issue. Sorry for the late reply: I saw your comment by accident. If you have any questions/issues/etc. on Galaxy, please contact us on Gitter https://gitter.im/galaxyproject/dev , or, again, feel free to open an issue. |
|
@ic4f, never too late ! Thanks for your reply. Cheers |
ic4f
added a commit
to ic4f/galaxy
that referenced
this issue
Apr 4, 2021
This appears to be creating a redundant join. The tool dependency is already eagerly loaded and the subqueryload joins the same tool_shed_repository that is already in the query. This causes a bug under SQLAlchemy 1.4: the deferred option is not applied to repository.metadata. (This reverts galaxyproject#8933)
ic4f
added a commit
to ic4f/galaxy
that referenced
this issue
Apr 4, 2021
This appears to be creating a redundant join. The tool dependency is already eagerly loaded and the subqueryload joins the same tool_shed_repository that is already in the query. This causes a bug under SQLAlchemy 1.4: the deferred option is not applied to repository.metadata. (This reverts galaxyproject#8933)
ic4f
added a commit
to ic4f/galaxy
that referenced
this issue
Apr 6, 2021
This appears to be creating a redundant join. The tool dependency is already eagerly loaded and the subqueryload joins the same tool_shed_repository that is already in the query. This causes a bug under SQLAlchemy 1.4: the deferred option is not applied to repository.metadata. (This reverts galaxyproject#8933)
ic4f
added a commit
to ic4f/galaxy
that referenced
this issue
Apr 7, 2021
This appears to be creating a redundant join. The tool dependency is already eagerly loaded and the subqueryload joins the same tool_shed_repository that is already in the query. This causes a bug under SQLAlchemy 1.4: the deferred option is not applied to repository.metadata. (This reverts galaxyproject#8933)
ic4f
added a commit
to ic4f/galaxy
that referenced
this issue
Apr 9, 2021
This appears to be creating a redundant join. The tool dependency is already eagerly loaded and the subqueryload joins the same tool_shed_repository that is already in the query. This causes a bug under SQLAlchemy 1.4: the deferred option is not applied to repository.metadata. (This reverts galaxyproject#8933)
ic4f
added a commit
to ic4f/galaxy
that referenced
this issue
Apr 9, 2021
This appears to be creating a redundant join. The tool dependency is already eagerly loaded and the subqueryload joins the same tool_shed_repository that is already in the query. This causes a bug under SQLAlchemy 1.4: the deferred option is not applied to repository.metadata. (This reverts galaxyproject#8933)
ic4f
added a commit
to ic4f/galaxy
that referenced
this issue
Apr 30, 2021
This appears to be creating a redundant join. The tool dependency is already eagerly loaded and the subqueryload joins the same tool_shed_repository that is already in the query. This causes a bug under SQLAlchemy 1.4: the deferred option is not applied to repository.metadata. (This reverts galaxyproject#8933)
ic4f
added a commit
to ic4f/galaxy
that referenced
this issue
May 5, 2021
This appears to be creating a redundant join. The tool dependency is already eagerly loaded and the subqueryload joins the same tool_shed_repository that is already in the query. This causes a bug under SQLAlchemy 1.4: the deferred option is not applied to repository.metadata. (This reverts galaxyproject#8933)
ic4f
added a commit
to ic4f/galaxy
that referenced
this issue
May 13, 2021
This appears to be creating a redundant join. The tool dependency is already eagerly loaded and the subqueryload joins the same tool_shed_repository that is already in the query. This causes a bug under SQLAlchemy 1.4: the deferred option is not applied to repository.metadata. (This reverts galaxyproject#8933)
ic4f
added a commit
to ic4f/galaxy
that referenced
this issue
May 18, 2021
This appears to be creating a redundant join. The tool dependency is already eagerly loaded and the subqueryload joins the same tool_shed_repository that is already in the query. This causes a bug under SQLAlchemy 1.4: the deferred option is not applied to repository.metadata. (This reverts galaxyproject#8933)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
The fix is to eagerload the child tool_dependency to tool shed repository relation as well.
The text was updated successfully, but these errors were encountered: