Fix crashes from non-epoch timestamps in kanban
Cluster 97455 · dashboard. Data as of
Nothing open on GitHub. Fix merged in #137209 on 12 Oct 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 #137209. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
resolved, deciding PR #137209. That is separate from the fix event. - Still open
- Nothing open on GitHub.
These items address a bug where non-epoch or legacy timestamp values stored in INTEGER columns cause kanban commands to crash. The fixes apply coercion of those timestamp values at read time.
Open issues0
Open PRs0
Fixes on record
-
#137209 fix(kanban): kanban show and dispatcher sweeps survive text run/event timestamps (#97455, salvage #97462)
files:
hermes_cli/kanban_db.py,hermes_cli/kanban_db_dispatch.py,hermes_cli/kanban_ops.py,tests/hermes_cli/test_kanban_cli.py,tests/hermes_cli/test_kanban_review_lifecycle_complete.py
2 PRs closed without merging
From the close comments: done elsewhere 1 · duplicate 1
Closed issues · 1
- Closed#97455[Bug]: Non-epoch timestamps written into INTEGER columns make `kanban show` crash with `invalid literal for int()
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
- dashboard
- Merged PRs
- #137209
- Closed issues
- 1
- Attempts
- 2 PRs closed without merging
- Fix link checked
- 12 Oct 2026