Fleet restart obligation discharge and lifecycle fixes
NousResearch/hermes-agent · cluster 119367
Data as of
Nothing open on GitHub. Fix merged in #120143. Check it covers your case.
The short answer
- Known?
- Yes. 5 related items grouped here, 1 issue already closed.
- Fix event
- A fix was merged to main in PR #120143. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
resolved, deciding PR #120143. That is separate from the fix event. - Still open
- Nothing open on GitHub.
These items address bugs in how fleet restart obligations are tracked and discharged, particularly when host commits diverge from expected SHAs via cherry-picks or local commits, plus fixes ensuring lifecycle commands target the correct profile.
Open issues0
Open PRs0
Fixes on record
-
#120143 fix: dashboard, tui-gateway and CLI lifecycle verbs act on the right profile (multiplexer, not the sticky/served one)
files:
hermes_cli/sessions_repair_profiles.py,hermes_cli/update_cmd_fleet.py,hermes_cli/update_cmd_fleet_checkout.py,hermes_cli/web_server_gateway.py,hermes_state_profile_repair.py,tests/hermes_cli/test_gateway_multiplex_served_record.py,tests/hermes_cli/test_sessions_repair_profiles.py,tests/hermes_cli/test_update_fleet_restart_pending.py,tests/tui_gateway/test_fast_session_scope.py,tests/tui_gateway/test_tui_gateway_server.py,tui_gateway/methods_config_set.py -
#120740 fix(update): a Desktop-only host settles an inventory-less restart obligation
files:
hermes_cli/update_cmd_fleet.py,hermes_cli/update_cmd_fleet_gatewayless.py,tests/hermes_cli/test_manual_serve_deferral.py,tests/hermes_cli/test_update_scoped_reconciliation.py,website/docs/getting-started/updating.md
2 PRs closed without merging
From the close comments: done elsewhere 1 · superseded by another PR 1
Closed issues · 1
- Closed#119367fleet_restart_pending / host restart obligation is permanently undischargeable after out-of-band HEAD movement (cherry-pick / local commit), and the armed-obligation veto preempts the #117051 receipt-settle path
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.40: 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