Cairn

Preventing concurrent writable database opens causing corruption

NousResearch/hermes-agent · cluster 107688

Data as of

Nothing open on GitHub. Fix merged in #108076. Check it covers your case.

The short answer

0open issues
0open PRs
5items grouped
Known?
Yes. 5 related items grouped here, 1 issue already closed.
Fix event
A fix was merged to main in PR #108076. Check it covers your case. No release data is tracked.
Tracker
The maintainers' tracker marks this resolved, deciding PR #108076. That is separate from the fix event.
Still open
Nothing open on GitHub.

These issues and PRs address a pattern where multiple components open the session/state database with write access simultaneously, which can trigger concurrent full-text-search rebuild corruption. The work focuses on making secondary openers read-only to ensure only one writable owner exists at a time.

Open issues0

No open issues.

Open PRs0

No open pull requests.

Fixes on record

Merged to main. A stamp counts the issues a fix is linked to.

  • #108076 state.db no longer gets a second writer from profile gateways, the dashboard, the lifecycle guard or doctor --fix (#102120 #107688 #102589 #107440; salvage #103489 #102682 #108012 #105428)

    merged to main

    files: contributors/emails/[redacted:email], cron/lifecycle_guard.py, gateway/hosted_room_policy_checkpoint.py, gateway/hosted_rooms.py, hermes_cli/doctor_state.py, hermes_cli/web_server_lifecycle.py, hermes_state_holders.py, tests/cron/test_lifecycle_guard_live_db.py, tests/gateway/test_hosted_rooms.py, tests/hermes_cli/test_doctor_wal_holder_guard.py, tests/hermes_cli/test_web_server.py, tests/state/test_fts_holder_instance_scope.py, tests/tui_gateway/test_groups_methods.py, tests/tui_gateway/test_hosted_room_service.py, tui_gateway/hosted_room_service.py

3 PRs closed without merging

From the close comments: duplicate 1 · merged via another change 1 · other 1

  • #107691 fix(dashboard): keep SessionDB read-only to avoid concurrent FTS corruption · other → 1caab41, #107974, #107701
  • #107701 fix(dashboard): eager session-store reconcile opens read-only, removing second writable owner · merged via another change → #107974, #107691
  • #107729 fix(dashboard): eager session-store reconcile opens read-only to avoid concurrent FTS rebuilds (#107688) · duplicate → #107701, #107688, #107691
Closed issues · 1
  • Closed#107688Dashboard does an unconditional writable SessionDB open at startup, exposing the documented concurrent-FTS-rebuild corruption vector
How this cluster was grouped
  • Link evidence (structural links throughout): every member is connected by structural evidence: shared changed files, or a closing/superseded reference.
  • Pairwise link density 0.40: the share of item pairs that carry a link, counting a structural link in full and a relevance-only link at 0.36. 1.00 means every pair is linked.

Pick up a Lab task

Check whether a fix covers the open issues here, with your own agent. Bring back evidence for maintainers.

Open the Lab

At a glance

Merged PRs
#108076
Closed issues
1
Attempts
3 PRs closed without merging
Fix link checked
11 Sep 2026

For your agent

The same facts, typed.

cluster/107688.json
cluster/107688.md