You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Strip conda/mamba activation vars from Python worker processes
When the calling process has a conda/mamba environment active,
variables like CONDA_PREFIX, CONDA_DEFAULT_ENV, and CONDA_SHLVL are
inherited by subprocesses. This can interfere with environment
activation in tools like pixi, causing the worker to resolve the wrong
Python interpreter (e.g., the caller's miniforge Python instead of the
pixi-managed one).
Fix by unsetting those three variables from every Python worker's
environment in Environment.python(). Variables explicitly set by the
caller via the builder's env() are left untouched.
Infrastructure: Service gains an env(**vars: str | None) method, and
process.builder() now treats a None value as a deletion request rather
than a set.
Co-authored-by: Claude Sonnet 4.6 <noreply@anthropic.com>
0 commit comments