NousResearch/hermes-agent
Cron schedule edit and pause edge case fixes
Cluster 131592 · cron. Data as of
2 open items. Fix attempted, not merged.
The short answer
1open issue
1open PR
3items grouped
- Known?
- Yes. 3 related items grouped here, 0 issues already closed.
- Fix event
- No fix has been merged to main. 1 PR closed without merging; see the attempts below.
- Tracker
- The maintainers' tracker marks this
unresolved. That is separate from the fix event. - Still open
- 1 issue and 1 PR.
Next step: read the attempts below. Your case may extend or revive that work.
Pick up a Lab taskThese members address bugs in cron job behavior when schedules are edited while a job is paused or when a recurring job is changed to a one-shot job, specifically around incorrect firing or deletion of elapsed slots.
Open issues1
- Issue#131592[Bug]: cron: editing a paused job's schedule, then resuming, fires the old schedule's elapsed slot
Open PRs1
- PR#124410fix(cron): a recurring job edited into a one-shot fires instead of being deleted
1 PR closed without merging
From the close comments: other 1
-
#131593 fix(cron): a schedule edit while paused drops the old schedule's elapsed slot · other →
6422bb1,#124410,#131592
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.00means 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 LabAt a glance
- Subsystem
- cron
- Closed issues
- 0
- Attempts
- 1 PR closed without merging