Unknown DB columns breaking session message reads
Cluster 116510. Data as of
Nothing open on GitHub. Fix merged in #116756 on 20 Sep 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 #116756. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
resolved, deciding PR #116756. That is separate from the fix event. - Still open
- Nothing open on GitHub.
These items address a bug where unexpected or unknown binary/BLOB columns in the messages table cause failures when reading session messages via the API. The fix involves handling or dropping such columns before data reaches the API layer.
Open issues0
Open PRs0
Fixes on record
-
#116756 fix(state): session transcripts survive an unknown binary column in messages (#116510, salvage #116527)
files:
hermes_state_messages.py,tests/hermes_state/test_hermes_state.py
2 PRs closed without merging
From the close comments: merged via another change 1 · partial fix 1
Closed issues · 1
- Closed#116510SELECT * in message reads lets a new column break GET /api/sessions/{id}/messages
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
- Merged PRs
- #116756
- Closed issues
- 1
- Attempts
- 2 PRs closed without merging
- Fix link checked
- 20 Sep 2026