Hardening lifecycle guard against NUL-bearing paths
Cluster 78942. Data as of
Nothing open on GitHub. Fix merged in #80258 on 6 Aug 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 #80258. 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 items address a crash in the lifecycle guard caused by NUL-encoded script paths, tracking the problem and iterating on fixes that sanitize input at different stages of processing.
Open issues0
Open PRs0
Fixes on record
-
#80258 fix(cron): make the lifecycle guard total — sanitize at ingestion, not per-syscall
files:
cron/lifecycle_guard.py,cron/scheduler.py,tests/cron/test_cron_no_agent.py,tests/hermes_cli/test_gateway_restart_loop.py,tools/terminal_tool.py
1 PR closed without merging
From the close comments: superseded by another PR 1
-
#79019 fix: harden lifecycle guard against NUL-encoded script paths (#78942) · superseded by another PR →
#80258,#76762,#77703,#77780,#78256
Closed issues · 1
- Closed#78942lifecycle_guard: NUL-bearing candidate path still crashes the guard at _read_referenced_script (incomplete #76762)
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
- #80258
- Closed issues
- 1
- Attempts
- 1 PR closed without merging
- Fix link checked
- 6 Aug 2026