Cron repeat defaults bug fix when schedule kind changes
NousResearch/hermes-agent · cluster 106096
Data as of
Nothing open on GitHub. Fix merged in #106532. Check it covers your case.
The short answer
- Known?
- Yes. 6 related items grouped here, 1 issue already closed.
- Fix event
- A fix was merged to main in PR #106532. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
resolved, deciding PR #106532. That is separate from the fix event. - Still open
- Nothing open on GitHub.
These members primarily address a bug where changing a cron job's schedule from one-shot to recurring (or vice versa) fails to re-derive the appropriate repeat defaults, causing incorrect firing behavior. One unrelated member about compaction batch summarization is also present.
Open issues0
Open PRs0
Fixes on record
-
#106532 Cron schedule changed from one-shot to recurring keeps firing instead of retiring after one run (#106096, salvage #106106)
files:
cron/jobs.py,tests/cron/test_jobs.py -
#106533 Compaction keeps batch clarify answers for the summarizer (#106077, salvage #106089)
files:
agent/context_compressor.py,contributors/emails/[redacted:email],tests/agent/test_context_compressor.py
3 PRs closed without merging
From the close comments: closed without comment 1 · done elsewhere 1 · merged via another change 1
-
#106106 fix(cron): re-derive repeat defaults when a schedule update flips the kind · merged via another change →
ae65399,#106532 - #106172 fix(cron): re-derive repeat default when schedule kind changes · closed without comment
-
#106174 fix(cron): re-derive repeat default when schedule kind changes (#106096) · done elsewhere →
ae65399,#106532,#106106,#106077,#106089,#106533
Closed issues · 1
- Closed#106096cron: update_job keeps repeat.times=1 when a one-shot schedule is changed to a recurring one, so the "recurring" job fires once and completes
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.33: 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 Lab