NousResearch/hermes-agent

Kanban SQLite DB corruption under concurrent access

Cluster 33267 · gateway. Data as of

2 open items. Fix attempted, not merged.

The short answer

1open issue
1open PR
3items grouped
Known?
Yes. 3 related items grouped here, 1 issue already closed.
Fix event
No fix has been merged to main. see the attempts below.
Tracker
The maintainers' tracker marks this unresolved. That is separate from the fix event.
Still open
1 issue and 1 PR.

This cluster centers on SQLite database corruption in the kanban module occurring under multi-process, multi-gateway, or high-concurrency conditions, particularly in WAL mode. Members include bug reports, hardening fixes, serialization approaches, and some adjacent concerns about storage backend flexibility and journal mode fallbacks.

Open issues1

  • Issue#38185[Feature]: The kanban module (hermes_cli.kanban_db) is hardcoded to SQLite only !

Open PRs1

  • PR#33366fix(gateway): dispatch kanban through configured store
Closed issues · 1
  • Closed#33267DB-ADAPTER-006: Kanban storage backend needs concurrency-safe adapter boundary
How this cluster was grouped
  • Link evidence (partly structural links): some members are connected by structural evidence (shared changed files, or a closing/superseded reference); the rest are joined by an automated relevance judgement over their text.
  • Members outside that structural core may belong to a different underlying problem.
  • Pairwise link density 0.45: 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
gateway
Closed issues
1
Attempts
0 PRs closed without merging

For your agent

The same facts, typed.