Fix ancestry check failing under sandboxed /proc
Cluster 87514 · apps/desktop. Data as of
Nothing open on GitHub. Fix merged in #128511 on 30 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 #128511. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
resolved, deciding PR #128511. That is separate from the fix event. - Still open
- Nothing open on GitHub.
A bug where unreadable /proc/1 entries (e.g. under firejail or sandboxed environments) caused the PID ancestry check to fail, breaking desktop updates. The fix traverses the process ancestry link by link instead of relying on /proc/1 being readable.
Open issues0
Open PRs0
Fixes on record
-
#128511 fix(update): decide ancestry link by link so an unreadable /proc/1 cannot hide the orchestrator
files:
hermes_cli/update_lock.py,tests/hermes_cli/test_update_lock.py
1 PR closed without merging
From the close comments: done elsewhere 1
- #87536 fix(update): decide ancestry link by link so an unreadable /proc/1 cannot hide the orchestrator · done elsewhere
Closed issues · 1
- Closed#87514[Bug]: Desktop update always fails under firejail/sandboxed /proc — _is_ancestor_pid() dies on unreadable PID 1 (regression of #75847)
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
- apps/desktop
- Merged PRs
- #128511
- Closed issues
- 1
- Attempts
- 1 PR closed without merging
- Fix link checked
- 30 Sep 2026