Increase timeout to 45s #1823
Merged
Increase timeout to 45s #1823
Conversation
This file contains 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
Several users have experienced `OperationalError`s because the database has been locked. Whilst these errors relate to the builder, it's proving hard to recreate them locally. It's not the case, for example, that making many updates to a single codelist in a short space of time locks the database. Finding the route cause of the errors will take time. However, given that the error has occurred 55 times in the last 30 days, increasing the timeout from 30s to 45s and monitoring the errors seems reasonable. Thanks to @emprestige for reporting the errors in the first instance. Closes #1811
StevenMaude
approved these changes
Jan 30, 2024
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.
Several users have experienced
OperationalErrors because the database has been locked. Whilst these errors relate to the builder, it's proving hard to recreate them locally. It's not the case, for example, that making many updates to a single codelist in a short space of time locks the database.Finding the route cause of the errors will take time. However, given that the error has occurred 55 times in the last 30 days, increasing the timeout from 30s to 45s and monitoring the errors seems reasonable.
Thanks to @emprestige for reporting the errors in the first instance.
Closes #1811