VSCode does not properly load env vars for environment created with micromamba executable #24490
Labels
bug
Issue identified by VS Code Team member as probable bug
triage-needed
Needs assignment to the proper sub-team
Environment data
Notes:
I alias micromamba to mamba, so anywhere where it says mamba can be replaced with micromamba. I am using the stand-alone executable for micromamba. I've also replaced personal information with XXX where applicable.
Code Snippet
Repro Steps
Supporting Info
#1 Micromamba env not activated beforehand - Notice that there is only one conda-related env var available. There are a few env vars and site packages related errors in the jupyter log.
#2 Micromamba venv activated in cli first then VSCode launched with "code" - Many more env vars available as well as important ones for geospatial work like GDA_DATA and GDAL_DRIVER_PATH. Env vars and site packages related errors are still showing, but the issue is resolved and the data query works with no crashes.
#3 Micromamba env not activated beforehand - but now miniforge3 is also installed on the same pc. - There seems to be a mix of miniforge and mamba env vars. Env vars and site packages related errors are gone for some reason.
The text was updated successfully, but these errors were encountered: