Reactivating terminal message in loop #22494

Efryed · 2023-11-19T04:11:46Z

Efryed
Nov 19, 2023

Hello, I just created a new profile using the python option, when I open a project, a message appears about reactivating the terminal but I don't know what it refers to. If I run the program with the button it seems to run using the virtual environment, so I guess it is not a serious problem.

Edit:
It seems that when I modify a file a message appears about analyzing but it stays in loop anyway.

Answered by Efryed

Nov 19, 2023

Hi, seems like when I created a profile using the python template by default this install the pre-release version of python and pylance extensions, when I change to release version, all works fine.

View full answer

Efryed · 2023-11-19T06:19:31Z

Efryed
Nov 19, 2023
Author

Hi, seems like when I created a profile using the python template by default this install the pre-release version of python and pylance extensions, when I change to release version, all works fine.

0 replies

brettcannon · 2023-11-21T19:49:35Z

brettcannon
Nov 21, 2023
Collaborator

Converted to an issue: #22512 .

2 replies

DuTim Nov 23, 2023

I seem a same question :

2023-11-23 11:24:09.228 [info] Experiment 'pythonPromptNewFormatterExt' is active
2023-11-23 11:24:09.228 [info] Experiment 'pythonPromptNewToolsExt' is active
2023-11-23 11:24:09.228 [info] Experiment 'pythonRecommendTensorboardExt' is active
2023-11-23 11:24:09.228 [info] Experiment 'pythonREPLSmartSend' is active
2023-11-23 11:24:09.228 [info] Experiment 'pythonTerminalEnvVarActivation' is active
2023-11-23 11:24:09.228 [info] Experiment 'pythonTestAdapter' is active
2023-11-23 11:24:09.228 [debug] Getting roots
2023-11-23 11:24:09.228 [debug] Getting roots
2023-11-23 11:24:09.228 [debug] Found roots
2023-11-23 11:24:09.228 [debug] Start watching file for changes /root/.conda/environments.txt
2023-11-23 11:24:09.228 [debug] Start watching: /root/.conda with pattern environments.txt using VSCode API
2023-11-23 11:24:09.228 [debug] Removing invalid env from cache C:\PROGRAMDATA\MINICONDA3\ENVS\MAIN\PYTHON.EXE
2023-11-23 11:24:09.228 [debug] Removing invalid env from cache C:\PROGRAMDATA\MINICONDA3\PYTHON.EXE
2023-11-23 11:24:09.228 [debug] Found roots
2023-11-23 11:24:09.228 [debug] Start watching root /nfs1/xz_yyb/xz for globs ["python","*/python","*/bin/python"]
2023-11-23 11:24:09.228 [debug] Start watching: /nfs1/xz_yyb/xz with pattern python using VSCode API
2023-11-23 11:24:09.228 [debug] Start watching: /nfs1/xz_yyb/xz with pattern */python using VSCode API
2023-11-23 11:24:09.228 [debug] Start watching: /nfs1/xz_yyb/xz with pattern */bin/python using VSCode API
2023-11-23 11:24:09.380 [info] Default formatter is set to ms-python.black-formatter for workspace /nfs1/xz_yyb/xz
2023-11-23 11:24:09.436 [debug] Waiting for test server to start...
2023-11-23 11:24:09.823 [debug] No cached env found for /root/miniconda3/envs/xz_llm/bin/python
2023-11-23 11:24:10.522 [info] Test server listening.
2023-11-23 11:24:10.522 [debug] Test server started.
2023-11-23 11:24:10.522 [debug] Testing: Setting up watcher for /nfs1/xz_yyb/xz
2023-11-23 11:24:10.532 [debug] Searching for conda.
2023-11-23 11:24:10.533 [debug] Probing conda binary: conda
2023-11-23 11:24:10.534 [debug] Dump environment variables {
    "MAIL": "/var/mail/root",
    "USER": "root",
    "SSH_CLIENT": "127.0.0.1 36268 22",
    "LANGUAGE": "en_US:",
    "SHLVL": "2",
    "HOME": "/root",
    "DBUS_SESSION_BUS_ADDRESS": "unix:path=/run/user/0/bus",
    "LOGNAME": "root",
    "_": "/root/.vscode-server/bin/1a5daa3a0231a0fbba4f14db7ec463cf99d7768e/bin/code-server",
    "XDG_SESSION_ID": "869",
    "VSCODE_AGENT_FOLDER": "/root/.vscode-server",
    "XDG_RUNTIME_DIR": "/run/user/0",
    "LANG": "en_US.UTF-8",
    "SHELL": "/bin/bash",
    "LC_ALL": "en_US.UTF-8",
    "PWD": "/root",
    "SSH_CONNECTION": "127.0.0.1 36268 127.0.0.1 22",
    "VSCODE_HANDLES_SIGPIPE": "true",
    "VSCODE_AMD_ENTRYPOINT": "vs/workbench/api/node/extensionHostProcess",
    "VSCODE_HANDLES_UNCAUGHT_ERRORS": "true",
    "VSCODE_NLS_CONFIG": "{\"locale\":\"en\",\"osLocale\":\"en\",\"availableLanguages\":{}}",
    "BROWSER": "/root/.vscode-server/bin/1a5daa3a0231a0fbba4f14db7ec463cf99d7768e/bin/helpers/browser.sh",
    "VSCODE_CWD": "/root",
    "ELECTRON_RUN_AS_NODE": "1",
    "VSCODE_IPC_HOOK_CLI": "/run/user/0/vscode-ipc-443cac21-2ad9-402b-bdf8-b547afd7b19f.sock",
    "PATH": "/root/.vscode-server/bin/1a5daa3a0231a0fbba4f14db7ec463cf99d7768e/bin/remote-cli:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin"
}
2023-11-23 11:24:10.536 [info] > conda info --json
2023-11-23 11:24:10.536 [debug] Worker id 1 for file plainExec.worker.js with data {"file":"conda","args":["info","--json"],"options":{"timeout":45000,"useWorker":true}}
2023-11-23 11:24:10.885 [debug] Failed to spawn conda binary conda Error: spawn conda ENOENT
    at ChildProcess._handle.onexit (node:internal/child_process:283:19)
    at onErrorNT (node:internal/child_process:476:16)
    at process.processTicksAndRejections (node:internal/process/task_queues:82:21)
2023-11-23 11:24:10.888 [debug] Probing conda binary: /root/.conda/bin/conda
2023-11-23 11:24:10.889 [info] > ~/.conda/bin/conda info --json
2023-11-23 11:24:10.889 [debug] Worker id 2 for file plainExec.worker.js with data {"file":"/root/.conda/bin/conda","args":["info","--json"],"options":{"timeout":45000,"useWorker":true}}
2023-11-23 11:24:10.976 [debug] Proposed API is not available, failed to subscribe to onDidExecuteTerminalCommand [Error: Extension 'ms-python.python' CANNOT use API proposal: terminalExecuteCommandEvent.
Its package.json#enabledApiProposals-property declares: contribEditorContentMenu, quickPickSortByLabel, portsAttributes, testObserver, quickPickItemTooltip, terminalDataWriteEvent, saveEditor but NOT terminalExecuteCommandEvent.
 The missing proposal MUST be added and you must start in extension development mode or use the following command line switch: --enable-proposed-api ms-python.python
	at y (/root/.vscode-server/bin/1a5daa3a0231a0fbba4f14db7ec463cf99d7768e/out/vs/workbench/api/node/extensionHostProcess.js:122:45185)
	at a.onDidExecuteTerminalCommand (/root/.vscode-server/bin/1a5daa3a0231a0fbba4f14db7ec463cf99d7768e/out/vs/workbench/api/node/extensionHostProcess.js:140:30549)
	at h._isWorking (/root/.vscode-server/extensions/ms-python.python-2023.21.13261010/out/client/extension.js:2:767705)
	at c.value (/root/.vscode-server/extensions/ms-python.python-2023.21.13261010/out/client/extension.js:2:282811)
	at h.isWorking (/root/.vscode-server/extensions/ms-python.python-2023.21.13261010/out/client/extension.js:2:767130)
	at x.activate (/root/.vscode-server/extensions/ms-python.python-2023.21.13261010/out/client/extension.js:2:759820)
	at /root/.vscode-server/extensions/ms-python.python-2023.21.13261010/out/client/extension.js:2:2455
	at Array.map (<anonymous>)
	at g.activateWorkspace (/root/.vscode-server/extensions/ms-python.python-2023.21.13261010/out/client/extension.js:2:2445)]
2023-11-23 11:24:10.979 [debug] No cached env found for /root/miniconda3/envs/xz_llm/bin/python
2023-11-23 11:24:10.980 [debug] No cached env found for /root/miniconda3/envs/xz_llm/bin/python
2023-11-23 11:24:11.233 [debug] Failed to spawn conda binary /root/.conda/bin/conda Error: spawn /root/.conda/bin/conda ENOENT
    at ChildProcess._handle.onexit (node:internal/child_process:283:19)
    at onErrorNT (node:internal/child_process:476:16)
    at process.processTicksAndRejections (node:internal/process/task_queues:82:21)
2023-11-23 11:24:11.233 [debug] Probing conda binary: /root/Miniconda3-py39_23.5.2-0-Linux-x86_64.sh/bin/conda
2023-11-23 11:24:11.234 [info] > ~/Miniconda3-py39_23.5.2-0-Linux-x86_64.sh/bin/conda info --json
2023-11-23 11:24:11.234 [debug] Worker id 3 for file plainExec.worker.js with data {"file":"/root/Miniconda3-py39_23.5.2-0-Linux-x86_64.sh/bin/conda","args":["info","--json"],"options":{"timeout":45000,"useWorker":true}}
2023-11-23 11:24:11.607 [error] Error in worker /root/.vscode-server/extensions/ms-python.python-2023.21.13261010/out/client/plainExec.worker.js Error: spawn ENOTDIR
    at ChildProcess.spawn (node:internal/child_process:413:11)
    at spawn (node:child_process:776:9)
    at t._workerPlainExecImpl (/root/.vscode-server/extensions/ms-python.python-2023.21.13261010/out/client/plainExec.worker.js:1:2069)
    at /root/.vscode-server/extensions/ms-python.python-2023.21.13261010/out/client/plainExec.worker.js:1:140045
    at /root/.vscode-server/extensions/ms-python.python-2023.21.13261010/out/client/plainExec.worker.js:1:140318
    at Object.<anonymous> (/root/.vscode-server/extensions/ms-python.python-2023.21.13261010/out/client/plainExec.worker.js:1:140339)
    at Module._compile (node:internal/modules/cjs/loader:1254:14)
    at Module._extensions..js (node:internal/modules/cjs/loader:1308:10)
    at Module.load (node:internal/modules/cjs/loader:1117:32)
    at Module._load (node:internal/modules/cjs/loader:958:12) {
  errno: -20,
  code: 'ENOTDIR',
  syscall: 'spawn'
}
2023-11-23 11:24:11.608 [debug] Failed to spawn conda binary /root/Miniconda3-py39_23.5.2-0-Linux-x86_64.sh/bin/conda Error: spawn ENOTDIR
    at ChildProcess.spawn (node:internal/child_process:413:11)
    at spawn (node:child_process:776:9)
    at t._workerPlainExecImpl (/root/.vscode-server/extensions/ms-python.python-2023.21.13261010/out/client/plainExec.worker.js:1:2069)
    at /root/.vscode-server/extensions/ms-python.python-2023.21.13261010/out/client/plainExec.worker.js:1:140045
    at /root/.vscode-server/extensions/ms-python.python-2023.21.13261010/out/client/plainExec.worker.js:1:140318
    at Object.<anonymous> (/root/.vscode-server/extensions/ms-python.python-2023.21.13261010/out/client/plainExec.worker.js:1:140339)
    at Module._compile (node:internal/modules/cjs/loader:1254:14)
    at Module._extensions..js (node:internal/modules/cjs/loader:1308:10)
    at Module.load (node:internal/modules/cjs/loader:1117:32)
    at Module._load (node:internal/modules/cjs/loader:958:12) {
  errno: -20,
  code: 'ENOTDIR',
  syscall: 'spawn'
}
2023-11-23 11:24:11.608 [debug] Probing conda binary: /root/miniconda3/bin/conda
2023-11-23 11:24:11.609 [info] > ~/miniconda3/bin/conda info --json
2023-11-23 11:24:11.609 [debug] Worker id 4 for file plainExec.worker.js with data {"file":"/root/miniconda3/bin/conda","args":["info","--json"],"options":{"timeout":45000,"useWorker":true}}
2023-11-23 11:24:11.618 [debug] Worker id 3 exited with code 1
2023-11-23 11:24:12.454 [debug] Clearing context for python dependencies not installed: ms-python.python.Python
2023-11-23 11:24:12.454 [debug] No cached env found for /root/miniconda3/envs/xz_llm/bin/python
2023-11-23 11:24:55.919 [debug] Worker id 1 exited with code 0
2023-11-23 11:24:56.268 [debug] Worker id 2 exited with code 0
2023-11-23 11:24:59.609 [debug] Failed to spawn conda binary /root/miniconda3/bin/conda [Error: Launching '/root/miniconda3/bin/conda info --json' timed out
	at _.getInfoImpl (/root/.vscode-server/extensions/ms-python.python-2023.21.13261010/out/client/extension.js:2:595455)
	at async _.locate (/root/.vscode-server/extensions/ms-python.python-2023.21.13261010/out/client/extension.js:2:594543)]
2023-11-23 11:24:59.632 [debug] Probing conda binary: /root/miniconda3/bin/conda
2023-11-23 11:24:59.635 [info] > ~/miniconda3/bin/conda info --json
2023-11-23 11:24:59.635 [debug] Worker id 5 for file plainExec.worker.js with data {"file":"/root/miniconda3/bin/conda","args":["info","--json"],"options":{"timeout":45000,"useWorker":true}}

brettcannon Nov 23, 2023
Collaborator

@DuTim please comment on the issue I opened.

I have now locked this discussion to direct people towards the issue.

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

Reactivating terminal message in loop #22494

Uh oh!

{{title}}

Uh oh!

Uh oh!

{{editor}}'s edit

{{editor}}'s edit

Uh oh!

Replies: 2 comments 2 replies

Uh oh!

{{title}}

Uh oh!

Uh oh!

{{title}}

Uh oh!

Uh oh!

{{title}}

Uh oh!

Uh oh!

{{title}}

Uh oh!

Select a reply

Uh oh!

Uh oh!

Reactivating terminal message in loop #22494

Uh oh!

Uh oh!

Efryed Nov 19, 2023

Replies: 2 comments · 2 replies

Uh oh!

Efryed Nov 19, 2023 Author

Uh oh!

brettcannon Nov 21, 2023 Collaborator

Uh oh!

DuTim Nov 23, 2023

Uh oh!

brettcannon Nov 23, 2023 Collaborator

Efryed
Nov 19, 2023

Replies: 2 comments 2 replies

Efryed
Nov 19, 2023
Author

brettcannon
Nov 21, 2023
Collaborator

brettcannon Nov 23, 2023
Collaborator