Cairn
NousResearch/hermes-agent

Cron fenced delivery claim ownership bug fixes

Cluster 95307. 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 items address a bug where finite cron jobs with bot-chat delivery incorrectly reported 'Fire claim ownership lost' and discarded results. The fixes preserve claim state during fenced delivery and correct how fence contention is interpreted.

Open issues0

No open issues.

Open PRs0

No open pull requests.

2 PRs closed without merging

From the close comments: done elsewhere 2

  • #95432 fix(cron): fence contention no longer reads as fire-claim ownership loss · done elsewhere → 9a60a7f, #95307
  • #104286 fix(cron): preserve claim during fenced delivery · done elsewhere → 9a60a7f
Closed issues · 1
  • Closed#95307[Bug]: cron — result of finite jobs (once / repeat-limited) discarded as "Fire claim ownership lost" when bot-chat delivery is configured
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.

cluster/95307.json
cluster/95307.md