Cron one-shot CLI orphaning and stale claim fixes
Cluster 86721. Data as of
Nothing open on GitHub. Fix merged in #86853. Check it covers your case.
The short answer
- Known?
- Yes. 5 related items grouped here, 1 issue already closed.
- Fix event
- A fix was merged to main in PR #86853. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
resolved, deciding PR #86853. That is separate from the fix event. - Still open
- Nothing open on GitHub.
These issues and PRs address a problem where running a cron job via a one-shot CLI command leaves the job stuck in a 'claimed' state permanently, because the async process dies with the calling process. The fixes involve waiting for completion instead of detaching and reaping stale or dead-owner claims.
Open issues0
Open PRs0
Fixes on record
-
#86853 fix(cron): stop one-shot CLI cron run from orphaning the job; reap dead-owner claims on tick
files:
cron/scheduler.py,hermes_cli/cron.py,tests/cron/test_dead_owner_claim_reclaim.py -
#86899 fix(cron): reap stale execution claims at the manual-run dispatch point (#86721)
files:
tests/cron/test_cron_run_stale_claim_reap_86721.py,tools/cronjob_tools.py
2 PRs closed without merging
From the close comments: done elsewhere 1 · merged via another change 1
Closed issues · 1
- Closed#86721cron run from one-shot CLI orphans the job: async delegation dies with the calling process, execution stuck 'claimed' forever
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.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