Cron DST transition duration scheduling bug fix
Cluster 109411. Data as of
Nothing open on GitHub. Fix merged in #109532 on 13 Sep 2026. Check it covers your case.
The short answer
- Known?
- Yes. 3 related items grouped here, 1 issue already closed.
- Fix event
- A fix was merged to main in PR #109532. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
resolved, deciding PR #109532. That is separate from the fix event. - Still open
- Nothing open on GitHub.
These items address a bug where cron duration schedules compute incorrect next-run times across daylight saving time transitions. The work focuses on preserving elapsed durations and wall-clock hours correctly when DST changes occur.
Open issues0
Open PRs0
Fixes on record
-
#109532 fix(cron): hold wall-clock cron hours and real elapsed intervals across DST (salvage #98553, #109414 + qwen-code#11723 guard)
files:
contributors/emails/[email protected],contributors/emails/[redacted:email],cron/jobs.py,tests/cron/test_compute_next_run_dst.py,tests/cron/test_duration_dst.py
1 PR closed without merging
From the close comments: merged via another change 1
-
#109414 fix(cron): preserve elapsed durations across DST changes · merged via another change →
#109532,#98553
Closed issues · 1
- Closed#109411cron: duration schedules compute the wrong next-run instant across DST transitions
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
- Merged PRs
- #109532
- Closed issues
- 1
- Attempts
- 1 PR closed without merging
- Fix link checked
- 13 Sep 2026