Cairn

Cron zero-interval validation to prevent runaway jobs

NousResearch/hermes-agent · cluster 55727 · cron

Data as of

4 open items. Fix attempted, not merged.

The short answer

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

These issues and pull requests concern a bug where cron schedules with zero-duration intervals (e.g., 'every 0m') are accepted and trigger runaway repeated execution. The work focuses on adding validation to reject such zero or sub-minute intervals.

Open issues1

  • Issue#55727Cron 'every 0m' interval is accepted and re-fires every tick (runaway job)

Open PRs3

  • PR#55726fix(cron): reject sub-minute recurring intervals (every 0m runaway)
  • PR#55751fix(cron): reject zero-interval schedules (every 0m/every 0h)
  • PR#55990fix(cron): reject zero-duration intervals to prevent runaway jobs (#55727)
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.50: 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
0
Attempts
0 PRs closed without merging

For your agent

The same facts, typed.

cluster/55727.json
cluster/55727.md