cron worker and systemd scope cache revalidation fixes
Cluster 110803. Data as of
Nothing open on GitHub. Fix merged in #111484 on 15 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 #111484. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
resolved, deciding PR #111484. That is separate from the fix event. - Still open
- Nothing open on GitHub.
These items address a bug where the cron restart-safe worker silently fails after a user bus disappears due to a permanently cached systemd scope probe, along with related fixes to revalidate scope availability instead of repeatedly failing.
Open issues0
Open PRs0
Fixes on record
-
#111484 fix(cron): restart-safe worker names a vanished user bus and re-probes instead of failing every tick with exit 1 (#110803, salvage #110808)
files:
cron/scheduler.py,tests/cron/test_restart_safe_worker.py,tests/tools/test_process_registry.py,tools/process_registry.py
1 PR closed without merging
From the close comments: closed without comment 1
- #110808 fix(tools): revalidate systemd scope availability · closed without comment
Closed issues · 1
- Closed#110803[Bug]: cron restart-safe worker silently fails after user bus disappears; permanent scope-probe cache never revalidates
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
- #111484
- Closed issues
- 1
- Attempts
- 1 PR closed without merging
- Fix link checked
- 15 Sep 2026