launchd gateway restart skipped during update
Cluster 74973 · hermes cli. Data as of
Nothing open on GitHub. Fix merged in #92963 on 25 Aug 2026. Check it covers your case.
The short answer
- Known?
- Yes. 4 related items grouped here, 1 issue already closed.
- Fix event
- A fix was merged to main in PR #92963. 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 issues and PRs address a bug where a booted-out launchd gateway is silently skipped during the update process, causing the update to exit successfully with the gateway dead and deregistered. Related work also extends update planning so missed restart-phase runtimes are tracked and fail the update rather than going unnoticed.
Open issues0
Open PRs0
Fixes on record
-
#92902 feat(update): planned runtimes the restart phase misses now fail the update — plan becomes the worklist (#91277 Phase 2, salvage #88949)
files:
hermes_cli/gateway.py,hermes_cli/update_cmd.py,hermes_cli/update_inventory.py,tests/hermes_cli/test_plan_reconciliation_windows_live.py,tests/hermes_cli/test_restart_plan_reconciliation.py,tests/hermes_cli/test_update_inventory.py,tests/hermes_cli/test_update_launchd_fleet_restart.py,tests/hermes_cli/test_update_launchd_restart_verification.py -
#92963 fix(update): booted-out launchd gateways get restarted, never silently skipped (#74973, salvage #75021)
files:
hermes_cli/update_cmd.py,tests/hermes_cli/test_update_launchd_restart_verification.py,tests/hermes_cli/test_update_launchd_unloaded_gateway.py
1 PR closed without merging
From the close comments: merged via another change 1
-
#75021 fix(update): restart a booted-out launchd gateway instead of skipping it (#74973) · merged via another change →
bee489d,#92963,#92902,#74973
Closed issues · 1
- Closed#74973[Bug]: macOS: hermes update silently skips the gateway restart when the launchd job is already booted out — update exits 0 with the gateway dead and deregistered
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.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