Conda run for my julia conda environment is run 30 times on startup.

[rchiodo]

VS Code version

1.63-insiders

Extension version

2022.0.1578295602-dev

OS type

Windows

OS version

Windows 10

Python distribution

Anaconda

Python version

3.9

Language server

Pylance

Expected behaviour

Maybe run conda run a couple of times.

Actual behaviour

Seems to be stuck in an infinite loop. I have dozens of these:

Chewing up all my CPU

Steps to reproduce

Conda julia environment? Not sure why.

Logs

python.logs.txt

Code of Conduct

• I agree to follow this project's Code of Conduct

[karrtikr]

I suspect 2 factors:

• If we fail to validate an env, we do not cache the output of the command, so I guess that's why it's run multiple times. (Although weirdly, according to the logs we only run the command once.)
• Validating conda envs now requires us to activate them which is taking longer than expected for these particular envs, hence node fails due to SIGTERM.

I'll create a PR to fix both of these.

[karrtikr]

Please try out https://github.com/microsoft/vscode-python/suites/4664902118/artifacts/126817679 which has the fix.

[rchiodo]

I don't think it fixed it. I still have 7 or 8 conda processes just spinning:

[karrtikr]

Can you export the conda environment to a yml file and provide it here? Does the logs still have the SIGTERM error?

[rchiodo]

Yep SIGTERM still happening:

[ERROR 2021-11-15 10:23:39.210]: [Error: Command failed: C:\Users\aku91\miniconda3\Scripts\conda.exe run -p C:\Users\Rich\.julia\conda\3 --no-capture-output python c:\Users\aku91\.vscode-insiders\extensions\ms-python.python-2022.0.1582521035-dev\pythonFiles\interpreterInfo.py

	at ChildProcess.exithandler (child_process.js:317:12)
	at ChildProcess.emit (events.js:315:20)
	at maybeClose (internal/child_process.js:1048:16)
	at Process.ChildProcess._handle.onexit (internal/child_process.js:288:5)] {
  killed: true,
  code: null,
  signal: 'SIGTERM',
  cmd: 'C:\\Users\\aku91\\miniconda3\\Scripts\\conda.exe run -p C:\\Users\\Rich\\.julia\\conda\\3 --no-capture-output python c:\\Users\\aku91\\.vscode-insiders\\extensions\\ms-python.python-2022.0.1582521035-dev\\pythonFiles\\interpreterInfo.py'
}

The conda environment is weird? I don't know how I got it (it looks like it's from a different user id on my machine).

# conda environments:
#
                         C:\Users\Rich\.julia\conda\3 <-- This is the failing one. It has no name?
base                     C:\Users\aku91\miniconda3
conda310                 C:\Users\aku91\miniconda3\envs\conda310
condaEnvTest             C:\Users\aku91\miniconda3\envs\condaEnvTest
condaTestQT5          *  C:\Users\aku91\miniconda3\envs\condaTestQT5
env                      C:\Users\aku91\miniconda3\envs\env
golden_scenario_env      C:\Users\aku91\miniconda3\envs\golden_scenario_env
ipykernel_test           C:\Users\aku91\miniconda3\envs\ipykernel_test
jupyterlabTest           C:\Users\aku91\miniconda3\envs\jupyterlabTest
python36                 C:\Users\aku91\miniconda3\envs\python36
python38_py2exe          C:\Users\aku91\miniconda3\envs\python38_py2exe
python38_pyinstaller     C:\Users\aku91\miniconda3\envs\python38_pyinstaller
testEmpty                C:\Users\aku91\miniconda3\envs\testEmpty
testSysPath              C:\Users\aku91\miniconda3\envs\testSysPath
testempty                C:\Users\aku91\miniconda3\envs\testempty

Maybe a bug in conda? Why is it listing that one?