Fix: Increase SQLite busy_timeout to 5 minutes to mitigate locking errors#240
Open
9chait9 wants to merge 2 commits into
Open
Fix: Increase SQLite busy_timeout to 5 minutes to mitigate locking errors#2409chait9 wants to merge 2 commits into
9chait9 wants to merge 2 commits into
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Fixes #238. Increased SQLite busy_timeout from 2 minutes (120000ms) to 5 minutes (300000ms) in src/db/index.ts to provide more buffer for concurrent read operations, especially when the WASM fallback is active and WAL mode is not available.
Test Plan
src/db/__tests__/index.test.ts.initializeandopenmethods ofDatabaseConnectionto verifybusy_timeoutis set to 300000ms.DatabaseConnectionclass such asgetDb,getPath,isOpen,close,transaction,getSize, andoptimizeare also covered by unit tests.