Cairn
NousResearch/hermes-agent

Fleet restart pending flag false positive fixes

Cluster 98588 · hermes cli. Data as of

1 open item. Fix merged in #111371 on 15 Sep 2026. Check it covers your case.

The short answer

1open issue
0open PRs
4items grouped
Known?
Yes. 4 related items grouped here, 0 issues 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
1 issue and 0 PRs.

These issues and pull requests address cases where the system incorrectly reports that gateways may still be serving pre-update modules after a restart has already occurred. The work focuses on correctly discharging or skipping the fleet restart pending state when gateways are verified to be serving the expected version.

Open issues1

  • Issue#98588False positive 'gateways may still be serving pre-update modules' after launchd respawn

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/[email protected], 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

2 PRs closed without merging

From the close comments: done elsewhere 2

  • #98612 fix(update): skip fleet restart when gateways already match current checkout · done elsewhere → 8130274, #111371, #98588, #109600
  • #105417 fix(update): discharge fleet_restart_pending when the fleet provably serves expected_sha · done elsewhere → 127214a, #111371
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.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
0
Attempts
2 PRs closed without merging
Fix link checked
15 Sep 2026

For your agent

The same facts, typed.

cluster/98588.json
cluster/98588.md