Gateway hash-suffix units not credited during restart reconciliation

NousResearch/hermes-agent · cluster 110238 · hermes cli

Data as of

3 open items. Fix attempted, not merged.

The short answer

1open issue
2open PRs
4items grouped
Known?
Yes. 4 related items grouped here, 0 issues already closed.
Fix event
No fix has been merged to main. 1 PR closed without merging; see the attempts below.
Tracker
The maintainers' tracker marks this unresolved. That is separate from the fix event.
Still open
1 issue and 2 PRs.

These issues and fixes address a bug where systemd gateway units with hash suffixes are not recognized during update reconciliation, causing false 'never touched' warnings and persistent fleet_restart_pending state. Multiple related cases are covered, including custom-home and default-profile gateways.

Open issues1

  • Issue#110238[Bug]: `hermes update` leaves fleet_restart_pending + prints false "never touched" warning when the systemd gateway unit name carries a hash suffix

Open PRs2

  • PR#110254fix(update): stop custom-home gateways from leaving restart pending
  • PR#110256fix(update): credit hash-suffixed gateway units in restart reconciliation

1 PR closed without merging

From the close comments: duplicate 1

  • #111066 fix(update): credit hashed gateway unit for default profile (#110238) · duplicate → #110250, #110238
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
Closed issues
0
Attempts
1 PR closed without merging

For your agent

The same facts, typed.