Fix launchers baking in scratch Python paths
Cluster 131745 · hermes cli. Data as of
Nothing open on GitHub. Fix merged in #132512 on 4 Oct 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 #132512. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
resolved, deciding PR #132512. That is separate from the fix event. - Still open
- Nothing open on GitHub.
A bug caused published launchers to bind against temporary scratch fixture interpreter paths rather than the installation's own store, leading to exit-127 crashes after reboot. These members address detection, prevention, and correction of that path-binding mistake.
Open issues0
Open PRs0
Fixes on record
-
#132512 fix(launchers): bind published launchers to the install's own store, not an inherited runtime dir
files:
hermes_cli/_launchers.py,hermes_cli/gateway.py,pm/environments.py,tests/hermes_cli/test_source_launcher_publication.py,tests/hermes_cli/test_update_launch_completion.py
2 PRs closed without merging
From the close comments: closed without comment 1 · superseded by another PR 1
Closed issues · 1
- Closed#131745[Bug] Launcher published against e2e scratch Python — gateway exit-127 crash loop after reboot
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 LabAt a glance
- Subsystem
- hermes cli
- Merged PRs
- #132512
- Closed issues
- 1
- Attempts
- 2 PRs closed without merging
- Fix link checked
- 4 Oct 2026