Skip to content

fix(state): increase SQLite busy timeout to 60 seconds - #1

Merged
lightcloud00 merged 1 commit into
mainfrom
fix/sqlite-busy-timeout-60s
Aug 22, 2026
Merged

fix(state): increase SQLite busy timeout to 60 seconds#1
lightcloud00 merged 1 commit into
mainfrom
fix/sqlite-busy-timeout-60s

Conversation

@lightcloud00

Copy link
Copy Markdown
Owner

Summary

Increase the SQLite pool busy timeout from five seconds to 60 seconds so transient cross-process locks do not abort Codex startup.

Change

-.busy_timeout(Duration::from_secs(5))
+.busy_timeout(Duration::from_secs(60))

No schema, migration, database-content, CLI-flag, or public configuration change is included.

Verification

  • repository formatter: just fmt
  • focused state tests: just test -p codex-state sqlite
  • downstream rust-v0.149.0 artifact: 9 SQLite-state tests and 3 CLI recovery tests passed
  • isolated seven-second BEGIN IMMEDIATE: stock failed with SQLite code 5; patched Codex waited, acquired the DB, and reached the TUI
  • real shared-state launch reached the authenticated prompt without signaling existing sessions
  • read-only PRAGMA quick_check returned ok for state_5.sqlite and logs_2.sqlite

Upstream issue: openai#35555.

@coderabbitai

coderabbitai Bot commented Aug 22, 2026

Copy link
Copy Markdown

Important

  • 🔍 Trigger review

This repository does not receive automatic reviews because it has fewer than 10 stars.

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: bcae6cb9-b145-49a0-a7cf-69e774fbe64d


Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant