Skip to content

fix: initialize SQLite before starting its connection pool - #22

Merged
nosam1998 merged 3 commits into
mainfrom
fix/sqlite-startup-lock
Sep 30, 2026
Merged

nosam1998 merged 3 commits into
mainfrom
fix/sqlite-startup-lock

Conversation

@nosam1998

@nosam1998 nosam1998 commented Sep 30, 2026 •

Copy link
Copy Markdown
Member

A real CLI startup in browser CI failed with SQLite database is locked. File-backed stores now configure WAL and apply migrations through a dedicated connection before constructing the multi-connection pool, avoiding background connection setup during schema writes. In-memory stores retain their sole connection while migrating.

Add a multithreaded regression test that repeatedly creates, writes, closes, and reopens 32 fresh databases, and verifies the in-memory path still preserves its schema. Existing atomic-write, concurrent-append, restart, and offline-query checks remain in CI. Rust CI, Web CI, and game benchmarks pass against current main. The regression covers 32 fresh database lifecycles; the dependent interactive-docs browser test also passes with this initialization.

@nosam1998
nosam1998 marked this pull request as ready for review September 30, 2026 19:48
@nosam1998
nosam1998 merged commit f1ff7e8 into main Sep 30, 2026
6 checks passed
@nosam1998
nosam1998 deleted the fix/sqlite-startup-lock branch October 2, 2026 06:07
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant