fix: SQLite3 queue pop atomicity - #86
Merged
michalsn merged 1 commit intoJul 23, 2026
Merged
Conversation
Copy link
Copy Markdown
Member
Sorry, something went wrong.
patel-vansh
approved these changes
May 21, 2026
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
Reviewers
1 more reviewer2 participants
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.
Description
This PR fixes SQLite queue popping so concurrent workers cannot claim the same pending job.
SQLite now uses BEGIN IMMEDIATE to acquire the write lock before selecting and reserving a job. Other database drivers keep the existing transaction and skip-locked behavior.
It also adds coverage for SQLite job claiming and documents busyTimeout for SQLite multi-worker setups.
Checklist: