#23397: fix(memory): raise qmd sqlite busy_timeout for read stability
size: XS
Cluster:
QMD Memory Management Fixes
## What
- change QMD SQLite `busy_timeout` from `1ms` to `5000ms`
- add a regression test that verifies `PRAGMA busy_timeout = 5000` is applied when opening the index DB
## Why
- `busy_timeout=1` is effectively no wait
- under normal qmd update writes, read queries can fail with `SQLITE_BUSY`
- this makes read-side memory search tolerant to short write lock contention
## Validation
- `pnpm check`
- `pnpm vitest run src/memory/qmd-manager.test.ts`
Most Similar PRs
#16917: fix(memory): close stale SQLite connection after qmd update
by zerone0x · 2026-02-15
67.2%
#9624: fix(memory): resolve QMD search returning empty results [AI-assisted]
by kowshik24 · 2026-02-05
62.6%
#11364: fix(memory/qmd): prevent cascading failure when query fails or retu...
by blazerui · 2026-02-07
61.1%
#19179: fix(memory): respect readonly mode in database initialization
by marliechorgan · 2026-02-17
61.0%
#11860: fix(memory): enable SQLite WAL mode for concurrent access safety
by Sojemand · 2026-02-08
60.7%
#9149: Fix: Allow QMD backend to work without OpenAI auth
by vishaltandale00 · 2026-02-04
60.6%
#23311: fix(memory): expose maxOutputChars as configurable qmd limit
by haitao-sjsu · 2026-02-22
60.1%
#20125: fix(doctor): skip memorySearch provider check when using QMD backend
by brandonwise · 2026-02-18
60.0%
#10801: fix: eagerly initialize QMD memory backend on gateway startup
by 1kuna · 2026-02-07
58.8%
#17910: feat(memory): QMD daemon mode — persistent process with idle lifecycle
by patrickshao · 2026-02-16
58.6%