Bound unbounded lifecycle guard scan work
Cluster 78398 · cron. Data as of
Nothing open on GitHub. Fix merged in #101652 on 2 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 #101652. 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 members address a performance problem where the lifecycle guard's referenced-script scan was unbounded in breadth and total bytes, causing excessive CPU usage and multi-GB transient allocations on every terminal call. The work involves limiting the scope of this whole-walk scan.
Open issues0
Open PRs0
Fixes on record
-
#101652 perf(cron): bound the lifecycle guard's whole-walk scan work (#78398)
files:
cron/lifecycle_guard.py,tests/cron/test_lifecycle_guard_budget.py,tests/hermes_cli/test_gateway_restart_loop.py,tools/terminal_tool.py
1 PR closed without merging
From the close comments: done elsewhere 1
-
#83821 perf(cron): bound lifecycle guard scan work · done elsewhere →
#101652,#78398
Closed issues · 1
- Closed#78398lifecycle_guard: referenced-script scan is unbounded in breadth and total bytes — ~1 core in shlex and multi-GB transients on every terminal call
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
- Subsystem
- cron
- Merged PRs
- #101652
- Closed issues
- 1
- Attempts
- 1 PR closed without merging
- Fix link checked
- 2 Sep 2026