Cairn
NousResearch/hermes-agent

systemd TimeoutStopSec cron drain budget sizing fix

Cluster 94759. Data as of

Nothing open on GitHub. Fix merged in #96445 on 27 Aug 2026. 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 #96445. Check it covers your case. No release data is tracked.
Tracker
The maintainers' tracker marks this resolved, deciding PR #96445. That is separate from the fix event.
Still open
Nothing open on GitHub.

A reported issue and several related fix attempts addressing the generated systemd unit's TimeoutStopSec not accounting for the cron drain timeout, causing premature SIGKILL during draining. The members represent the bug report and multiple iterations of the same patch.

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.

  • #96445 fix(gateway): size systemd TimeoutStopSec from the full stop budget incl. the cron drain floor (salvage of #94775)

    merged to main

    files: gateway/restart.py, gateway/run.py, gateway/shutdown_forensics.py, hermes_cli/gateway.py, tests/gateway/test_cron_drain_floor.py, tests/hermes_cli/test_gateway_service.py

3 PRs closed without merging

From the close comments: duplicate 1 · merged via another change 1 · superseded by another PR 1

  • #94770 fix(gateway): size TimeoutStopSec from the full stop budget incl. the cron floor · duplicate → #94775, #94759
  • #94775 fix(gateway): size systemd TimeoutStopSec from the full stop budget · merged via another change → #96445, #94770
  • #94808 fix(gateway): size systemd TimeoutStopSec from cron drain budget (#94759) · superseded by another PR → #94775, #94808
Closed issues · 1
  • Closed#94759Generated systemd unit's TimeoutStopSec ignores cron_drain_timeout — systemd SIGKILLs an in-budget drain
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

Merged PRs
#96445
Closed issues
1
Attempts
3 PRs closed without merging
Fix link checked
27 Aug 2026

For your agent

The same facts, typed.

cluster/94759.json
cluster/94759.md