Cairn

Cron recovery for live but deadlocked workers

NousResearch/hermes-agent · cluster 115692

Data as of

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

These issues and PRs address a scenario where a cron job's claim is held by a worker process that is alive but deadlocked (e.g. stuck in futex_wait), preventing subsequent runs. The work involves detecting, warning about, and reclaiming such stuck claims using wall-clock or progress-based guards.

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.

  • #117185 Cron reclaims a live-but-deadlocked worker's claim once it outlives the derived stale bound (#115692, salvage #116549 + #115696)

    merged to main

    files: cron/constants.py, cron/executions.py, cron/jobs.py, cron/scheduler.py, tests/cron/test_dead_owner_claim_reclaim.py, tests/cron/test_stale_running_recovery.py, tools/cronjob_tools.py

3 PRs closed without merging

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

  • #115696 fix(cron): warn on stuck live-owned claims without reaping · merged via another change → 2d08676, #117185
  • #116253 fix(cron): reclaim live workers that stop making progress · superseded by another PR → #117185
  • #116549 fix(cron): wall-clock stale-claim guard for live-but-deadlocked workers (#115692) · merged via another change → 2d08676, #117185
Closed issues · 1
  • Closed#115692Dead-owner cron recovery cannot clear a claim held by a live-but-deadlocked worker (futex_wait), blocking every subsequent run
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
#117185
Closed issues
1
Attempts
3 PRs closed without merging
Fix link checked
20 Sep 2026

For your agent

The same facts, typed.

cluster/115692.json
cluster/115692.md