new Jupyter Notebook project: interpreter hangs and never starts

[midleman]

System details:

Positron and OS details:

Positron Version: 2025.02.0 (Universal) build 14
Code - OSS Version: 1.95.0
Commit: 8ecd4c5d2ac4645dbc9d8fb02e2b4c855eb02cfe
Date: 2025-01-08T02:44:17.090Z
Electron: 32.2.1
Chromium: 128.0.6613.186
Node.js: 20.18.0
V8: 12.8.374.38-electron.0
OS: Darwin arm64 24.2.0

Describe the issue:

Interpreter hangs/never starts after creating new Jupyter Notebook project via New Project Wizard.

Steps to reproduce the issue:

1. Select New > New Project... > Jupyter Notebook
2. Click through New Project Wizard leaving all the default values.
3. Verify Jupyter project opens - PASS
4. Verify interpreter starts - FAIL

Video

Screen.Recording.2025-01-08.at.10.24.25.AM.mov

Expected or desired behavior:

Actual: Interpreter is infinitely stuck in Starting up...
Expected: Interpreter should start up w/o issue.

Were there any error messages in the UI, Output panel, or Developer Tools console?

Is any of this relevant?

DEBUG [New project startup] Pending tasks changed to: {}
workbench.desktop.main.js:18413   ERR command 'python.createEnvironmentAndRegister' not found: Error: command 'python.createEnvironmentAndRegister' not found
    at $t2b2.n (vscode-file://vscode-app/Applications/Positron.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:334667:29)
    at $t2b2.executeCommand (vscode-file://vscode-app/Applications/Positron.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:334662:17)
    at async $Kvc2.M (vscode-file://vscode-app/Applications/Positron.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:607324:24)
    at async $Kvc2.F (vscode-file://vscode-app/Applications/Positron.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:607215:7)
    at async $Kvc2.y (vscode-file://vscode-app/Applications/Positron.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:607173:7)
    at async $Kvc2.w (vscode-file://vscode-app/Applications/Positron.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:607151:7)
workbench.desktop.main.js:18413   ERR spawn /Applications/Positron.app/Contents/Resources/app/extensions/positron-python/python-env-tools/bin/pet ENOENT: Error: spawn /Applications/Positron.app/Contents/Resources/app/extensions/positron-python/python-env-tools/bin/pet ENOENT
	at ChildProcess._handle.onexit (node:internal/child_process:286:19)
	at onErrorNT (node:internal/child_process:484:16)
	at process.processTicksAndRejections (node:internal/process/task_queues:82:21)

[jonvanausdeln]

I believe we've seen a similar issue on Python and R projects intermittently in CI only.

[juliasilge]

Do we expect the console to start the same interpreter as chosen for the notebook? Probably?

Also weird that there is a 1 in a cell by default.

[jthomasmock]

I do expect that both the console and notebook should respect the newly created environment and make use of it.