reembed_embeddings opened a bare SQLite connection with no busy timeout. Running it against the live DB, as for the #189 corpus re-embed, an UPDATE that met the watcher holding the write lock would fail at once with SQLITE_BUSY and abort the whole run (? on each update).
It now sets PRAGMA busy_timeout = 15000 after connecting, matching what the server waits on its own connections. Used for the 2026-11-03 prod re-embed of summaries, calendar and entities.
reembed_embeddings opened a bare SQLite connection with no busy timeout. Running it against the live DB, as for the #189 corpus re-embed, an UPDATE that met the watcher holding the write lock would fail at once with SQLITE_BUSY and abort the whole run (`?` on each update).
It now sets `PRAGMA busy_timeout = 15000` after connecting, matching what the server waits on its own connections. Used for the 2026-11-03 prod re-embed of summaries, calendar and entities.
🤖 Generated with [Claude Code](https://claude.com/claude-code)
The tool opened a bare connection, so an UPDATE that met the server's
watcher holding the write lock failed at once (SQLITE_BUSY) and aborted
the whole run. Wait up to 15 s instead, like the server's own pool.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
cameron
merged commit 6fffca9989 into master2026-11-03 19:55:52 +00:00
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
reembed_embeddings opened a bare SQLite connection with no busy timeout. Running it against the live DB, as for the #189 corpus re-embed, an UPDATE that met the watcher holding the write lock would fail at once with SQLITE_BUSY and abort the whole run (
?on each update).It now sets
PRAGMA busy_timeout = 15000after connecting, matching what the server waits on its own connections. Used for the 2026-11-03 prod re-embed of summaries, calendar and entities.🤖 Generated with Claude Code