# NousResearch/hermes-agent · Single-writer flock gate for state.db WAL safety

## Open now

- Nothing open on GitHub.

A reported bug and associated fix proposal address concurrent write access to state.db, where a second process (such as doctor --fix or schema repair) can corrupt the write-ahead log. The proposed mitigation is a lazy flock-based single-writer gate to serialize access.

## TL;DR

- 3 member(s): 0 open issue(s), 1 closed issue(s), 0 open PR(s), 1 merged PR(s), 1 PR(s) closed without merging.
- A fix was merged to main in PR #110914. Verify it addresses your case.
- **Recommended:** read PR #110914 (and any competing PRs below) before filing. Confirm the merged change covers your symptom.

## Maintainer resolution verdict

- Internal-tracker verdict over this cluster's issue members: `unresolved`. This is distinct from the fix status above. Weigh it yourself.

## How this cluster was grouped

- Link evidence (`STRUCTURAL_SPANNING`): every member is connected by structural evidence: shared changed files, or a closing/superseded reference.
- Pairwise link density `0.67`: the share of member 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.

## Closed / duplicate issues

- #103339: \[Bug\] Second writer via \`doctor --fix\` / \`repair_state_db_schema\` / hosted_rooms still corrupts live-WAL state.db — upstream guards are fail-open; proposing a lazy flock single-writer gate (field-verified)

## Prior & competing PRs

- **#110914: state.db maintenance from a second process refuses any live holder (doctor --fix checkpoint, schema repair; #103339 item 2)**. merged to main · fix tier `verified`
  - maintainer direction: category `merged`
  - files: `hermes_cli/doctor_state.py`, `hermes_state_holders.py`, `hermes_state_repair.py`, `tests/hermes_cli/test_doctor_wal_checkpoint_guard.py`, `tests/hermes_state/test_state_db_malformed_repair.py`, `tests/hermes_state/test_state_db_repair_non_destructive.py`, `tests/hermes_state/test_state_db_second_process_maintenance.py`
- **#109270: fix(state): implement lazy flock single-writer gate to prevent WAL corruption**. closed without merge
  - maintainer direction: category `implemented_elsewhere`; implication `superseded`; refs `9b419a2d3c`, `#110914`, `#103339`

## Fix status

- Merged to main in PR #110914 (cited above). No release data is tracked. Verify downstream.
- Fix last verified (merged) `2026-09-14`.