Stale restart-pending marker causes false warnings
NousResearch/hermes-agent · cluster 111272
Data as of
Nothing open on GitHub. Fix merged in #111371. Check it covers your case.
The short answer
- Known?
- Yes. 6 related items grouped here, 1 issue already closed.
- Fix event
- A fix was merged to main in PR #111371. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
resolved, deciding PR #111371. That is separate from the fix event. - Still open
- Nothing open on GitHub.
A cluster of bugs and fixes around the fleet_restart_pending marker not being cleared after a successful gateway update and restart. The work addresses false warnings at CLI startup and in hermes doctor, slow gateway boot timing, and conditions under which the marker is considered settled.
Open issues0
Open PRs0
Fixes on record
-
#111371 fix(update): fleet_restart_pending settles on a verified gateway serving the pulled sha; foreign state-file writers never read as current (#111272, #110420, salvage #110426 #105417)
files:
contributors/emails/[redacted:email],hermes_cli/update_cmd_fleet.py,hermes_cli/update_receipt.py,tests/gateway/test_control_socket.py,tests/hermes_cli/test_fleet_matrix_down_state.py,tests/hermes_cli/test_update_fleet_restart_pending.py,tests/hermes_cli/test_update_receipt.py -
#112259 hermes update no longer fails fleet verification on a slow gateway boot (fixes #111272, salvage #111385)
files:
hermes_cli/update_cmd_fleet.py,tests/hermes_cli/test_update_fleet_snapshot_settle.py
3 PRs closed without merging
From the close comments: done elsewhere 1 · won't fix / by design 1 · other 1
-
#111300 fix(cli): clear fleet_restart_pending when degraded probe is answered by marker SHA · other →
#111272 -
#111302 fix(update): settle fleet_restart_pending when the gateway already serves the pulled sha · won't fix / by design →
de16ce9,#105417,#111272 -
#111385 fix(update): wait for fleet state publication after supervised restart · done elsewhere →
f81c33c,#112259
Closed issues · 1
- Closed#111272bug(update): successful update + gateway restart leaves `fleet_restart_pending` marker — every CLI startup and `hermes doctor` print a false "did not restart running gateways" warning
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.33: 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