Cairn

launchd restart drain-aware SIGUSR1 signal path fix

NousResearch/hermes-agent · cluster 27745 · gateway

Data as of

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

The short answer

0open issues
0open PRs
6items grouped
Known?
Yes. 6 related items grouped here, 1 issue already closed.
Fix event
A fix was merged to main in PR #124009. 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 concern a bug where the macOS launchd-triggered gateway restart was not invoking the drain-aware SIGUSR1 graceful restart path, instead falling through to a non-drain SIGTERM. The members describe the problem and proposed fixes to wire the launchd restart correctly to the SIGUSR1 path.

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.

  • #124009 fix(gateway): restart wait no longer cuts off a cron drain (salvage #123878)

    merged to main

    files: gateway/restart.py, hermes_cli/gateway.py, hermes_cli/update_cmd_drain_report.py, hermes_cli/update_cmd_fleet.py, hermes_cli/update_receipt.py, tests/gateway/test_restart_after_turn.py

4 PRs closed without merging

From the close comments: done elsewhere 2 · PR volume cleanup 1 · stale or abandoned 1

  • #27781 fix(gateway): wire launchd_restart to drain-aware SIGUSR1 path (#27745) · stale or abandoned
  • #35178 fix(gateway): use drain-aware SIGUSR1 in launchd_restart · done elsewhere → 7a76046, 8afaab3, #27745, #124009
  • #36240 fix(cli): complete launchd restart after self-restart signal · PR volume cleanup
  • #77512 fix(gateway): use drain-aware SIGUSR1 in launchd restart from fresh shells · done elsewhere → 7a76046, 8afaab3, #124009
Closed issues · 1
  • Closed#27745macOS launchd: hermes gateway restart never invokes _graceful_restart_via_sigusr1, always takes non-drain SIGTERM path from fresh shells
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.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
gateway
Merged PRs
#124009
Closed issues
1
Attempts
4 PRs closed without merging
Fix link checked
26 Sep 2026

For your agent

The same facts, typed.

cluster/27745.json
cluster/27745.md