Nothing open on GitHub. Fix merged in #114755 on 18 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 #114755. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
resolved, deciding PR #114755. That is separate from the fix event. - Still open
- Nothing open on GitHub.
These items identify and address a drift problem in the cron ticker where sleeping after work causes jobs to fire progressively later over time. The proposed fixes replace sleep-after-work with sleep-to-deadline approaches to maintain a fixed period.
Open issues0
Open PRs0
Fixes on record
-
#114755 fix(cron): ticker fires on a fixed period instead of drifting later each tick (#114467, salvage #114473)
files:
contributors/emails/[redacted:email],cron/scheduler_provider.py,tests/cron/test_cron_ticker_drift.py
1 PR closed without merging
From the close comments: merged via another change 1
-
#114473 fix(cron): sleep to deadline in ticker loops to eliminate clock drift · merged via another change →
14b50a7,#114755,#114467,#114473
Closed issues · 1
- Closed#114467Cron ticker drifts: sleep-after-work means jobs fire progressively later
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
- #114755
- Closed issues
- 1
- Attempts
- 1 PR closed without merging
- Fix link checked
- 18 Sep 2026