Files
CyberStrikeAI/internal/database
Ordinary 9891b04215 fix: wait out SQLite busy on concurrent asset upserts
Deep mode fires many create_asset calls at once. UpsertAssets used a
DEFERRED transaction (SELECT then INSERT) on a 25-connection pool, so
writers hit SQLITE_BUSY immediately and returned "database is locked"
in a few milliseconds instead of waiting.

Open SQLite with _txlock=immediate and a 30s busy timeout, shrink the
pool, and retry locked upserts. Add a 32-way concurrent upsert test.
2026-10-16 12:20:21 +08:00
..
2026-08-18 20:34:53 +08:00
2026-08-18 20:34:53 +08:00
2026-08-18 20:34:53 +08:00
2026-08-18 20:34:53 +08:00
2026-08-18 20:34:53 +08:00
2026-08-18 20:34:53 +08:00
2026-08-18 20:34:53 +08:00
2026-08-18 20:34:53 +08:00
2026-08-18 20:34:53 +08:00
2026-08-18 20:34:53 +08:00
2026-08-18 20:34:53 +08:00
2026-08-18 20:34:53 +08:00
2026-08-18 20:34:53 +08:00
2026-08-18 20:34:53 +08:00
2026-08-18 20:34:53 +08:00
2026-08-18 20:34:53 +08:00
2026-08-18 20:34:53 +08:00
2026-08-18 20:34:53 +08:00
2026-08-18 20:34:53 +08:00
2026-08-18 20:34:53 +08:00
2026-08-18 20:34:53 +08:00
2026-08-18 20:34:53 +08:00
2026-08-18 20:34:53 +08:00
2026-08-18 20:34:53 +08:00
2026-08-18 20:34:53 +08:00
2026-08-18 20:34:53 +08:00
2026-08-18 20:34:53 +08:00
2026-08-18 20:34:53 +08:00