NousResearch/hermes-agent

SQLite WAL fallback handling for disk I/O errors in state database

Cluster 46797 · cron. Data as of

1 open item. Fix merged in #74485 on 30 Jul 2026. Check it covers your case.

The short answer

1open issue
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 #74485. 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
1 issue and 0 PRs.

Members appear to concern SQLite WAL journal mode handling, with several proposing that "disk I/O error" be treated as a WAL-incompatibility marker so the system falls back to DELETE journal mode. One also mentions a configurable journal_mode, and another reports state.db problems on ZFS with multiple connections.

Open issues1

  • Issue#46797fix: add "disk i/o error" to _WAL_INCOMPAT_MARKERS so stale-SHM/EIO after unclean shutdown falls back to DELETE journal mode

Open PRs0

No open pull requests.

Fixes on record

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

  • #74485 fix(state): configurable journal_mode + WAL-refusal detection cluster (salvages #68912, #57918, #46865, #55322)

    merged to main

    files: cli-config.yaml.example, contributors/emails/[redacted:email], hermes_cli/config_defaults.py, hermes_cli/kanban_db.py, hermes_state.py, tests/hermes_cli/test_kanban_db.py, tests/test_hermes_state.py, tests/test_hermes_state_wal_fallback.py, tests/test_journal_mode_config.py

2 PRs closed without merging

From the close comments: merged via another change 1 · superseded by another PR 1

  • #46967 [verified] fix: force WAL fallback to delete on disk i/o init failure · superseded by another PR → 5c49cd0, #74485
  • #55322 fix(gateway): add disk I/O error to WAL-fallback markers for ZFS · merged via another change → 5c49cd0, #74485
Closed issues · 1
  • Closed#55305Hermes Agent gateway on ZFS corrupts state.db with multiple connections
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.44: 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

Subsystem
cron
Merged PRs
#74485
Closed issues
1
Attempts
2 PRs closed without merging
Fix link checked
30 Jul 2026

For your agent

The same facts, typed.