Do not try to create revision if current transaction is under rollback. #919
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.
Reason
Good evening,
Thank you for creating awesome library!
At the moment I found one corner case that I can't workaround without monkey patching reversion library.
Let say we enabled reversion middleware for every view within the project.
Let say in a signal receiver a database exception was catched.
I'm aware that programmers should avoid catching exceptions inside atomic block.
Unfortunately, such code could be placed in a poorly-written third-party package that we are forced to use.
Expected behavior
Without reversion enabled such code block would rollback transaction and delegate execution to the view management code.
Real behavior
With reversion enabled the same code would fail with transaction management error.
You could see how written test would fail without transaction state check.
Suggested solution
After execution exists
yield
statement inside_create_revision_context
context manager we would place additional checks for current transaction state before trying to createRevision
object.Best regards,
Josiah.