Corrupt session data no longer crashes session listing
Cluster 102399. Data as of
Nothing open on GitHub. Fix merged in #108086 on 11 Sep 2026. Check it covers your case.
The short answer
- Known?
- Yes. 3 related items grouped here, 1 issue already closed.
- Fix event
- A fix was merged to main in PR #108086. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
resolved, deciding PR #108086. That is separate from the fix event. - Still open
- Nothing open on GitHub.
A single malformed row in the session database (bad timestamp, invalid JSON, or oversized query) previously caused the entire sessions list and related features to fail. These changes make session listing and related operations tolerant of corrupt individual rows.
Open issues0
Open PRs0
Fixes on record
-
#108086 state.db: one corrupt row (bad timestamp / malformed marker JSON / oversized IN-list) no longer kills sessions list, export, insights or prune (#102399 #102352 #99959 #94691 #106060; salvage #106071 #101726 #94701 #102679 #100658)
files:
agent/insights.py,hermes_cli/cli_session_mixin.py,hermes_cli/session_export.py,hermes_cli/session_export_html.py,hermes_cli/session_export_md.py,hermes_cli/session_filters.py,hermes_cli/sessions_cmd.py,hermes_cli/sessions_cmd_browse.py,hermes_cli/timefmt.py,hermes_state_common.py,hermes_state_compression.py,hermes_state_gateway.py,hermes_state_maintenance.py,hermes_state_messages.py,hermes_state_portability.py,hermes_state_schema.py,hermes_state_sessions.py,tests/hermes_state/test_corrupt_row_robustness.py,tests/test_hermes_state.py,tests/test_session_export_batch.py(+2 more)
1 PR closed without merging
From the close comments: stale or abandoned 1
- #102400 fix(cli): render corrupt timestamps as unknown instead of crashing sessions list · stale or abandoned
Closed issues · 1
- Closed#102399[Bug]: sessions list/browse dies with TypeError on a TEXT timestamp — one corrupt row kills the whole listing
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.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
- #108086
- Closed issues
- 1
- Attempts
- 1 PR closed without merging
- Fix link checked
- 11 Sep 2026