Corrupt timestamp and state DB resilience fixes
Cluster 91536 · apps/desktop. Data as of
Nothing open on GitHub. Fix merged in #122283 on 25 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 #122283. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
resolved, deciding PR #122283. That is separate from the fix event. - Still open
- Nothing open on GitHub.
These items address crashes and failures caused by corrupt or invalid timestamp values and malformed data in the state database. The work focuses on constraining bad values and preventing single corrupt rows from breaking sessions, export, insights, or prune operations.
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) -
#122283 fix(state): keep corrupt timestamp cells out of last_active and recovered databases
files:
hermes_cli/session_recovery.py,hermes_state_common.py,hermes_state_sessions.py,tests/hermes_cli/test_session_recovery_timestamps.py,tests/hermes_state/test_corrupt_row_robustness.py
1 PR closed without merging
From the close comments: superseded by another PR 1
-
#91543 fix(state): constrain last_active to a sane epoch window · superseded by another PR →
a241349,#108086
Closed issues · 1
- Closed#91536[Bug]: Sessions pane crashes with "Invalid time value" — recovery wrote garbage floats into messages.timestamp
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 Lab