Cairn
NousResearch/hermes-agent

Cron script timeout orphaned process tree cleanup

Cluster 71148 · cron. Data as of

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

These issues and pull requests address a problem where cron script timeouts fail to kill descendant processes, leaving orphaned process trees. Multiple fix attempts explore process-group and process-tree kill strategies to make cleanup bounded and complete.

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.

  • #93795 fix(cron): tree-kill script timeout descendants via agent.deadline.kill_process_tree (#85125 4a, salvage of #86791)

    merged to main

    files: contributors/emails/[redacted:email], contributors/emails/[redacted:email], cron/scheduler.py, tests/cron/test_cron_script.py

3 PRs closed without merging

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

  • #71152 fix(cron): kill whole process group on script timeout to prevent orphaned descendants (#71148) · done elsewhere → #93795, #85125, #86791, #71148
  • #71506 fix(cron): make script timeout process-tree cleanup bounded · superseded by another PR → a31be48, 011fad0, 326fa24, 51dd37f, #74123, #59379, #71506
  • #86791 fix(cron): tree-kill script timeout descendants via agent.deadline.kill_process_tree · merged via another change → #93795
Closed issues · 1
  • Closed#71148Cron script timeout leaves orphaned process trees (timeout kill doesn't reach descendants)
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

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

For your agent

The same facts, typed.

cluster/71148.json
cluster/71148.md