NousResearch/hermes-agent

Single-writer flock gate for state.db WAL safety

Cluster 103339. Data as of 2026-10-25 11:21 UTC

Nothing open on GitHub. Fix merged in #110914 on 14 Sep 2026. Check it covers your case.

open issues

open PRs

items grouped

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

Next step: read #110914, then check it covers your case.

Read #110914 Pick up a Lab task

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.

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.

#110914 state.db maintenance from a second process refuses any live holder (doctor --fix checkpoint, schema repair; #103339 item 2)

merged to main

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

1 PR closed without merging

From the close comments: done elsewhere 1

#109270 fix(state): implement lazy flock single-writer gate to prevent WAL corruption · done elsewhere → 9b419a2, #110914, #103339

Closed issues · 1

Closed#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)

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.67: 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: #110914
Closed issues: 1
Attempts: 1 PR closed without merging
Fix link checked: 14 Sep 2026

For your agent

The same facts, typed.

cluster/103339.json
cluster/103339.md