Update receipt and fleet restart loop fixes
NousResearch/hermes-agent · cluster 98022 · hermes cli
Data as of
Nothing open on GitHub. Fix merged in #103478. Check it covers your case.
The short answer
- Known?
- Yes. 7 related items grouped here, 1 issue already closed.
- Fix event
- A fix was merged to main in PR #103478. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
resolved, deciding PR #104153. That is separate from the fix event. - Still open
- Nothing open on GitHub.
Multiple fixes targeting bugs in the update system where stale or interrupted receipts caused fleet restarts to re-trigger indefinitely, and related issues with catch-up restart logic and receipt lifecycle management.
Open issues0
Open PRs0
Fixes on record
-
#103478 fix(update): fleet check no longer fails with "no rows" after stopping unmapped/dashboard-only runtimes; receipts survive the module purge (#97332, #98436, salvage #97350 #92934)
files:
contributors/emails/[redacted:email],hermes_cli/update_cmd_fleet.py,hermes_cli/update_cmd_maint.py,tests/hermes_cli/test_update_fleet_check_fail_closed.py,tests/hermes_cli/test_update_fleet_probe_resume_token.py,tests/hermes_cli/test_update_stale_module_purge.py -
#104153 fix(update): a successful update no longer re-arms the fleet restart forever (#98022, salvage #97547)
files:
hermes_cli/main.py,hermes_cli/update_cmd_fleet.py,hermes_cli/update_receipt.py,tests/hermes_cli/test_update_fleet_restart_pending.py,tests/hermes_cli/test_update_handoff_exit.py
4 PRs closed without merging
From the close comments: done elsewhere 1 · duplicate 1 · merged via another change 1 · other 1
-
#98526 fix(update): skip catchup fleet restart when interrupted receipt pulled SHA already matches checkout · done elsewhere →
#103414,#98022 - #98689 fix(update): dismiss stale receipt after catch-up fleet restart · other
-
#103499 fix(update): stop treating a clean command-boundary stop_reason as an interrupted update · merged via another change →
f58fcc8,#97547,#103478,#98022,#95294 -
#103677 fix(update): retire unfinished receipt after fleet restart catch-up · duplicate →
#95294,#98022,#100249,#103414,#97547,#103478
Closed issues · 1
- Closed#98022[Bug]: hermes update catch-up fleet restart (#95294 fix) re-fires on every run when update_receipts/latest.json is a stale interrupted receipt — fleet restarts forever even though it is already current
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.29: 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