[bugfix] Sqlite transaction escalation was causing errors #6299
Conversation
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
neacsu
approved these changes
Dec 18, 2025
jmwample
pushed a commit
that referenced
this pull request
Jan 7, 2026
* well that was an easy fix * change fn name because somebody wasn't happy about my one line fix
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.
Getting tickets from credential storage requires a transaction doing a read and then a write.
Running registration in parallel was causing sqlite to return errors, because it can't escalate two transactions, only one.
Fix : Declare said transaction as a write from the start, and the second one will wait for the first to complete
This change is