Silence retryable SQLite lock errors from docket.worker logger #19772
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.
closes #19771
PR #18957 added a log filter to suppress noisy SQLite "database is locked" errors from the
uvicorn.errorlogger. However, when usingflow.serve()with SQLite, background tasks likemark_deployments_readyrun through docket and log errors through thedocket.workerlogger, which was not covered by the original fix.This PR extends the existing SQLite lock log filter to also filter the
docket.workerlogger, silencing the harmless but alarming error messages that users see during onboarding.Changes
docket.workerlogger to the SQLite lock log filter installationChecklist
<link to issue>"mint.json.Human Review Checklist
docket.workeris the correct logger name for docket task execution errorsLink to Devin run: https://app.devin.ai/sessions/20e5e008a49b4757b66ba98ff91c9900
Requested by: Nate Nowack ([email protected]) (@zzstoatzz)