Cairn

fleet_restart_pending marker clearing bug fixes

NousResearch/hermes-agent · cluster 106682 · hermes cli

Data as of

Nothing open on GitHub. Fix merged in #111371. Check it covers your case.

The short answer

0open issues
0open PRs
5items grouped
Known?
Yes. 5 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 unresolved. That is separate from the fix event.
Still open
Nothing open on GitHub.

These items all address defects in the logic that retires or self-heals the fleet_restart_pending marker, covering cases where it was never cleared when gateways restarted outside the updater or already ran the expected SHA. The work also guards against foreign state-file writers being misread as current.

Open issues0

No open issues.

Open PRs0

No open pull requests.

Fixes on record

Merged to main. A stamp counts the issues a fix is linked to.

  • #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)

    merged to main

    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

3 PRs closed without merging

From the close comments: superseded by another PR 2 · done elsewhere 1

  • #106690 fix(update): retire fleet_restart_pending when live gateways match expected_sha · superseded by another PR → #105417, #100249
  • #106748 fix(update): retire fleet_restart_pending marker when live gateways match expected_sha · superseded by another PR → #105417
  • #107139 fix(update): self-heal fleet_restart_pending marker when fleet already runs expected SHA · done elsewhere → 127214a, #111371, #105417
Closed issues · 1
  • Closed#106682fix(update): fleet_restart_pending marker never cleared when gateways restart outside the updater
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.00 means 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

At a glance

Subsystem
hermes cli
Merged PRs
#111371
Closed issues
1
Attempts
3 PRs closed without merging
Fix link checked
15 Sep 2026

For your agent

The same facts, typed.

cluster/106682.json
cluster/106682.md