Nothing open on GitHub. Fix merged in #98275. Check it covers your case.
The short answer
- Known?
- Yes. 5 related items grouped here, 1 issue already closed.
- Fix event
- A fix was merged to main in PR #98275. Check it covers your case. No release data is tracked.
- 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 cron job creation or updates throw a TypeError when the repeat parameter is a string value like 'forever' instead of an integer. The fix involves normalizing string repeat values to prevent the type comparison error.
Open issues0
Open PRs0
Fixes on record
-
#98275 fix(cron): bare '30m' schedules recur as documented; 'in 30m' is the one-shot (salvage #78928)
files:
cron/jobs.py,tests/cron/test_claim_job_for_fire.py,tests/cron/test_jobs.py,tests/cron/test_oneshot_dispatch_failure_run_claim.py,tests/cron/test_terminal_job_rearm.py,tests/hermes_cli/test_web_server_cron_profiles.py,tests/test_timezone.py,tools/cronjob_tools.py,website/docs/user-guide/features/cron.md -
#98290 fix(cron): repeat='forever' no longer breaks job updates (completes the string-repeat class)
files:
cron/jobs.py,tests/cron/test_jobs.py,tools/cronjob_tools.py
2 PRs closed without merging
From the close comments: done elsewhere 2
Closed issues · 1
- Closed#71993Bug: cronjob create/update throws TypeError when repeat='forever' (string vs int comparison)
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.40: 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