Inverted liveness checks causing false dead reports
Cluster 94143. Data as of
Nothing open on GitHub. Fix merged in #96214 on 27 Aug 2026. Check it covers your case.
The short answer
- Known?
- Yes. 4 related items grouped here, 1 issue already closed.
- Fix event
- A fix was merged to main in PR #96214. 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.
A cluster of bugs and fixes around liveness/health checks that were incorrectly inverted or misapplied, causing running processes (cron gateway, stdio MCP children) to be falsely reported as dead or not running. Fixes address the probe logic and lock-based liveness detection.
Open issues0
Open PRs0
Fixes on record
-
#94339 fix(mcp): un-invert the stdio children liveness check
files:
tests/tools/test_mcp_stdio_children_dead.py,tools/mcp_tool.py -
#96214 fix(cron): trust the gateway runtime lock for builtin-ticker liveness (salvage #95947)
files:
contributors/emails/[redacted:email],hermes_cli/cron.py,tests/cron/test_87033_cronjob_gateway_liveness.py
1 PR closed without merging
From the close comments: superseded by another PR 1
-
#94155 fix(cron): stop the cronjob tool probing its own gateway as dead · superseded by another PR →
#96214,#95947,#13242,#94143,#94339
Closed issues · 1
- Closed#94143bug(cron): cronjob tool reports gateway_running: false from inside a running gateway (systemd user unit) — jobs DO fire
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 Lab