fix(persistence): enable WAL, busy_timeout, and FK on SQLite#101
Merged
RaghavChamadiya merged 1 commit intomainfrom Apr 26, 2026
Merged
fix(persistence): enable WAL, busy_timeout, and FK on SQLite#101RaghavChamadiya merged 1 commit intomainfrom
RaghavChamadiya merged 1 commit intomainfrom
Conversation
Two concurrent 'repowise update' invocations on the same workspace would trip 'sqlite3.OperationalError: database is locked' (#95). The default SQLite journal_mode is delete, which serialises writers and immediately fails any second writer instead of giving it a retry window. Register a 'connect' event listener on the SQLite-backed engines that runs on every new physical connection and sets: PRAGMA journal_mode = WAL (lets readers proceed during a write) PRAGMA synchronous = NORMAL (the safe pairing for WAL) PRAGMA busy_timeout = 5000 (5 seconds of polite back-off) PRAGMA foreign_keys = ON (matches PostgreSQL behaviour) WAL is a file-level setting that persists across opens, but the listener re-applies it defensively in case the database file was created by an older repowise version, alembic, or a third-party tool that left journal_mode at default. PostgreSQL engines are unchanged. Adds four unit tests covering each pragma plus a concurrent-writers test that fails on main with OperationalError.
swati510
approved these changes
Apr 26, 2026
Merged
RaghavChamadiya
added a commit
that referenced
this pull request
Apr 26, 2026
* feat: improve PreToolUse hook relevance with multi-signal search Replace FTS-only file retrieval with a 3-signal ranking system: - Symbol name match (weight 2.0) — most precise - File path match (weight 1.5) — catches path-based searches - FTS on wiki content (weight 1.0) — broadest, lowest priority Files ranked by signal score then PageRank, top 3 returned. Remove git signals (HOTSPOT, bus-factor, owner) from enrichment — that info belongs in get_risk, not every search. Remove Bash command interception (fragile regex on grep/rg commands). Keep: symbols (3), importers (3), dependencies (2) per file. * release: v0.3.1 Bumps repowise to 0.3.1 across pyproject.toml and the three sub-package __init__.py files. Highlights since 0.3.0: - Output language support for generated wiki content (#99) - Luau / Roblox language support (#89) - OpenRouter LLM and embedding provider (#56) - base_url plus per-provider env vars for OpenAI / Anthropic / Gemini / Ollama / LiteLLM (#85) - SQLite WAL plus busy_timeout plus FK constraints, fixing concurrent 'repowise update' database is locked errors (#101) - CLAUDE.md opt-out prompt now asked in both full and advanced modes and the answer is honoured (#102) - repowise init no longer silently overwrites unparseable user JSON configs (#94) - pyproject packages list resynced with the language-support refactor so editable installs and CI build cleanly (#97) - uv workflow documented and dev deps migrated to PEP 735 dependency-groups, silencing the tool.uv.dev-dependencies deprecation warning (#100) - Five Dependabot security bumps (dompurify, gitpython, mako, litellm, python-multipart) Also flips the project URLs and serve_cmd's _GITHUB_REPO constant from RaghavChamadiya/repowise to repowise-dev/repowise so 'repowise serve' can locate the published web UI tarball.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Closes #95.
Summary
Two concurrent `repowise update` invocations on the same workspace would trip `sqlite3.OperationalError: database is locked`. The default SQLite `journal_mode` is `delete`, which serialises writers and immediately fails any second writer instead of giving it a retry window.
What changed
Register a `connect` event listener on SQLite-backed engines that runs on every new physical connection and sets:
WAL is a file-level setting that persists across opens, but the listener re-applies it defensively in case the database file was created by an older repowise version, by alembic, or by a third-party tool that left `journal_mode` at the default.
PostgreSQL engines are unchanged.
Tests
Four unit tests in `tests/unit/persistence/test_database_pragmas.py`: