Timeout initiating sqlite #44
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
Qqwy
approved these changes
Jan 20, 2026
Contributor
Qqwy
left a comment
Qqwy
left a comment
There was a problem hiding this comment.
A trivial and non-spicy change. 
Contributor
Author
|
@OpsBotPrime merge! |
Contributor
|
Rebased as b334b3c, waiting for CI … |
Contributor
|
CI job 🟡 started. |
OpsBotPrime
force-pushed
the
reinier/timeout-initiating-sqlite
branch
from
b4a56bd to
b334b3c
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 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.
We are seeing sporadic startup failures from Opsqueue in CI. Meaning we don't see the webserver starting to listen on a socket.
We can only reason this originates from database initialisation, we therefore timeout the
open_and_setupcall in the server.