Self-referential .env variable growth causing E2BIG
Cluster 109902. Data as of
Nothing open on GitHub. Fix merged in #114427 on 17 Sep 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 #114427. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
resolved, deciding PR #114427. That is separate from the fix event. - Still open
- Nothing open on GitHub.
A bug where self-referential .env entries (e.g. PATH=/x:${PATH}) cause the variable to grow on every reload, eventually making environment too large for child process spawning. Multiple fixes and reports address making such reloads idempotent by resolving against a stable snapshot.
Open issues0
Open PRs0
Fixes on record
-
#114427 fix(env): self-referential .env values resolve once per process instead of growing on every reload
files:
contributors/emails/[email protected],hermes_cli/env_loader.py,tests/hermes_cli/test_env_loader_self_reference.py
2 PRs closed without merging
From the close comments: superseded by another PR 2
Closed issues · 1
- Closed#109902[Bug]: self-referential .env line (PATH=/x:${PATH}) grows on every reload until every child spawn dies with E2BIG
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
- Merged PRs
- #114427
- Closed issues
- 1
- Attempts
- 2 PRs closed without merging
- Fix link checked
- 17 Sep 2026