Cairn
NousResearch/hermes-agent

Strip CONDA_DEFAULT_ENV from subprocess environments

Cluster 58382 · environments. Data as of

2 open items. Fix attempted, not merged.

The short answer

1open issue
1open PR
3items grouped
Known?
Yes. 3 related items grouped here, 0 issues already closed.
Fix event
No fix has been merged to main. 1 PR closed without merging; see the attempts below.
Tracker
The maintainers' tracker marks this unresolved. That is separate from the fix event.
Still open
1 issue and 1 PR.

The members concern the CONDA_DEFAULT_ENV marker appearing in local or managed subprocess environments. One member reports the leak, and two titles refer to changes that strip the variable. The titles alone do not show whether any change was merged or whether the behavior is still present or has been fixed.

Open issues1

  • Issue#58382Local subprocess env leaks CONDA_DEFAULT_ENV marker

Open PRs1

  • PR#58383fix(env): strip Conda default env marker

1 PR closed without merging

From the close comments: duplicate 1

  • #58424 fix(env): strip CONDA_DEFAULT_ENV from managed subprocess environments (#58382) · duplicate
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.00 means 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

At a glance

Subsystem
environments
Closed issues
0
Attempts
1 PR closed without merging

For your agent

The same facts, typed.

cluster/58382.json
cluster/58382.md