Nothing open on GitHub. Fix merged in #131894 on 3 Oct 2026. Check it covers your case.
The short answer
0open issues
0open PRs
4items grouped
- Known?
- Yes. 4 related items grouped here, 1 issue already closed.
- Fix event
- A fix was merged to main in PR #131894. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
resolved, deciding PR #131894. That is separate from the fix event. - Still open
- Nothing open on GitHub.
These items all concern changing the log level for cron tick lock-skip messages from DEBUG to INFO so the events are visible in dual-scheduler setups. The group is coherent and focused on a single logging visibility concern.
Open issues0
Open PRs0
Fixes on record
-
#131894 fix(cron): log tick lock contention at INFO [risk 0.30]
files:
cron/scheduler.py
2 PRs closed without merging
From the close comments: done elsewhere 1 · duplicate 1
Closed issues · 1
- Closed#53720Cron tick log line is DEBUG-level; should be INFO for visibility in dual-scheduler setups
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.50: 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
- Merged PRs
- #131894
- Closed issues
- 1
- Attempts
- 2 PRs closed without merging
- Fix link checked
- 3 Oct 2026