Repository navigation
Fiddle: say where the uncommitted write was in ISOLATED_CONNECTION_AFTER_UNCOMMITTED_WRITES - #164
Closed
krishan711 wants to merge 1 commit into
Closed
krishan711 wants to merge 1 commit into
krishan711 wants to merge 1 commit into
Conversation
…TER_UNCOMMITTED_WRITES
Contributor
Author
|
Closing: wrong approach. |
This file contains hidden or 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
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.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
ISOLATED_CONNECTION_AFTER_UNCOMMITTED_WRITESis logged withstack_info=True, but JSON logs drop the stack, and the stack only shows where the isolated connection was opened, not where the write that blocks it happened.Database.executenow records the location of the first write on each connection (nearest three callers outsidecore.storeand sqlalchemy, asdir/file.py:line in function <- ...) and the error message includes it.The stack walk only runs for the first write per transaction.