NousResearch/hermes-agent

Cron heartbeat lock ordering deadlock fix

Cluster 106737. Data as of

Nothing open on GitHub. Fix attempted, not merged.

The short answer

0open issues
0open PRs
3items grouped
Known?
Yes. 3 related items grouped here, 1 issue already closed.
Fix event
No fix has been merged to main. 2 PRs closed without merging; see the attempts below.
Tracker
The maintainers' tracker marks this unresolved. That is separate from the fix event.
Still open
Nothing open on GitHub.

These members address an AB-BA deadlock caused by holding the fire-fence lock during heartbeat save_jobs operations. The proposed fix involves dropping or reordering that lock to prevent the deadlock condition.

Open issues0

No open issues.

Open PRs0

No open pull requests.

2 PRs closed without merging

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

  • #106745 fix(cron): do not hold fire fence during heartbeat save_jobs · merged via another change → 9a60a7f
  • #108772 fix(cron): drop fire-fence lock from heartbeat_fire_claim to break AB-BA deadlock (#106737) · duplicate → #106745, #106737, #108359
Closed issues · 1
  • Closed#106737Bug: heartbeat_fire_claim holds fire_fence_lock during save_jobs → false failed status
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.67: 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

Closed issues
1
Attempts
2 PRs closed without merging

For your agent

The same facts, typed.