Fix missing active=1 in hermes_state message INSERTs
Cluster 51646 · gateway. Data as of
Nothing open on GitHub. Fix merged in #60108 on 7 Jul 2026. Check it covers your case.
The short answer
- Known?
- Yes. 4 related items grouped here, 1 issue already closed.
- Fix event
- A fix was merged to main in PR #60108. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
resolved, deciding PR #60108. That is separate from the fix event. - Still open
- Nothing open on GitHub.
These issues and PRs address a bug where INSERT statements in hermes_state.py omit the active column, causing rows to have NULL values. Proposed fixes explicitly set active=1 in those INSERTs, with at least one variant also healing existing NULL rows on startup.
Open issues0
Open PRs0
Fixes on record
-
#60108 fix(state): set active=1 explicitly in message INSERTs + heal NULL rows on startup (#51646)
files:
hermes_state.py,tests/test_hermes_state.py
2 PRs closed without merging
From the close comments: partial fix 1 · other 1
Closed issues · 1
- Closed#51646[Bug]: Gateway Memory Loss — INSERT omits `active` column in `hermes_state.py`
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.50: the share of item pairs that carry a link, counting a structural link in full and a relevance-only link at 0.36.1.00means 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 LabAt a glance
- Subsystem
- gateway
- Merged PRs
- #60108
- Closed issues
- 1
- Attempts
- 2 PRs closed without merging
- Fix link checked
- 7 Jul 2026