Cairn
NousResearch/hermes-agent

Cron double-fire race condition fixes and tests

Cluster 51329 · cron. 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 race condition causing cron jobs to fire twice when concurrent schedulers overlap or in-flight guards are not yet registered. Includes fixes for duplicate execution, skipped manual trigger consumption, and a regression test.

Open issues0

No open issues.

Open PRs0

No open pull requests.

2 PRs closed without merging

From the close comments: done elsewhere 1 · other 1

  • #51452 test(cron): add regression test for double-fire race condition #51329 · done elsewhere → eb9cde7, #62684
  • #62684 fix(cron): prevent concurrent duplicate fires · other
Closed issues · 1
  • Closed#51329Cron double-fire: race between tick dispatch and in-flight guard registration
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

Subsystem
cron
Closed issues
1
Attempts
2 PRs closed without merging

For your agent

The same facts, typed.

cluster/51329.json
cluster/51329.md