b0a6a456ba
Some checks failed
CI / Check version consistency (push) Successful in 4s
CI / Check for .beads changes (push) Has been skipped
CI / Test (ubuntu-latest) (push) Failing after 8m12s
CI / Lint (push) Failing after 2m40s
CI / Test Nix Flake (push) Failing after 54s
Deploy Documentation / build (push) Failing after 2m15s
Deploy Documentation / deploy (push) Has been skipped
Nightly Full Tests / Full Test Suite (push) Failing after 36m33s
CI / Test (macos-latest) (push) Has been cancelled
CI / Test (Windows - smoke) (push) Has been cancelled
The ensureStoreActive() function was ignoring the user-configured --lock-timeout flag and always using the 30s default via sqlite.New(). This fix changes ensureStoreActive() to use sqlite.NewWithTimeout() with the configured lockTimeout, allowing users to specify shorter timeouts for multi-agent scenarios. With this change, users can now run: bd --lock-timeout=500ms sync to fail fast if the database is locked, rather than waiting 30s. Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
3.2 KiB
3.2 KiB