Cron scheduler stalls silently on EMFILE errors
Cluster 87644 · cron. Data as of
Nothing open on GitHub. Fix merged in #88335 on 17 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 #88335. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
resolved, deciding PR #88335. That is separate from the fix event. - Still open
- Nothing open on GitHub.
These issues and PRs concern a bug where the cron scheduler permanently stalls when an EMFILE (too many open files) error occurs, while the heartbeat continues to report healthy status. The work focuses on surfacing and properly escalating this error instead of silently stalling.
Open issues0
Open PRs0
Fixes on record
-
#88335 fix(cron): scheduler self-heals after EMFILE instead of stalling silently (salvage #87796)
files:
cron/scheduler.py,cron/scheduler_provider.py,hermes_cli/cron.py,tests/cron/test_cron_emfile_stall_87644.py
2 PRs closed without merging
From the close comments: closed without comment 1 · superseded by another PR 1
Closed issues · 1
- Closed#87644gateway: cron scheduler permanently stalls after EMFILE while heartbeat keeps reporting healthy
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 LabAt a glance
- Subsystem
- cron
- Merged PRs
- #88335
- Closed issues
- 1
- Attempts
- 2 PRs closed without merging
- Fix link checked
- 17 Aug 2026