Follow-up to #137: _txlock=immediate holds the write lock for the whole migration pass; four racing migrators on a slow CI disk exceeded the 5s busy timeout (Dev job 2285 SQLITE_BUSY). Local tier only; waits instead of erroring. Refs: Dev PR #325, plan KTD8.
Follow-up to #137: _txlock=immediate holds the write lock for the whole migration pass; four racing migrators on a slow CI disk exceeded the 5s busy timeout (Dev job 2285 SQLITE_BUSY). Local tier only; waits instead of erroring. Refs: Dev PR #325, plan KTD8.
Why: with _txlock=immediate the whole migration pass holds the write lock; four racing migrators on a slow CI disk exceeded the 5s busy timeout (job 2285: SQLITE_BUSY in TestMigrateRacingSQLite) although the local tier passes.
Evidence: go test -count=3 on the migration atomicity suite green locally; CI failure log cited in the Dev PR.
Impact: local SQLite tier only - lock contention waits up to 30s instead of erroring; no schema or API change.
Refs: Dev PR #325; plan KTD8.
weichen
merged commit efbd7b1d04 into main2026-10-11 03:42:55 +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.
Follow-up to #137: _txlock=immediate holds the write lock for the whole migration pass; four racing migrators on a slow CI disk exceeded the 5s busy timeout (Dev job 2285 SQLITE_BUSY). Local tier only; waits instead of erroring. Refs: Dev PR #325, plan KTD8.