ci: stop services before database writes to prevent SQLite lock - #137
Merged
Merged
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.
Summary
Stop the Daphne webserver and runner services before running use-case installations, and start them again afterward.
Why
The previous fix (running
sharpie-installfrom thewebserver/directory) resolved the "no such table" error by pointing to the correct database file. However, it exposed a new error:sqlite3.OperationalError: database is locked. SQLite only allows one writer at a time, and the running Daphne process was holding a write lock ondb.sqlite3during use-case installation.By stopping services before database writes and starting them after, we eliminate concurrent write access to the SQLite database.