Repository navigation
Start Native Python REPL errors: UNKNOWN notebook type: jupyter-notebook #24593
Copy link
Copy link
Closed as not planned
Closed as not planned
Copy link
Labels
area-replbugIssue identified by VS Code Team member as probable bugIssue identified by VS Code Team member as probable bugneeds spikeLabel for issues that need investigation before they can be worked on.Label for issues that need investigation before they can be worked on.
Description
Discussed in #24590
Originally posted by ChiNoel-osu December 11, 2024
When I try to start the REPL it shows this error message:

Smart send (Shift+Enter) gives the same error message:

This was working before, I was just using it, and I have no idea why it suddenly stopped working.
2024-12-12 11:55:02.185 [error] Error: UNKNOWN notebook type: jupyter-notebook
at VUe.f (vscode-file://vscode-app/c:/Users/victor1.wang/AppData/Local/Programs/Microsoft%20VS%20Code/resources/app/out/vs/workbench/workbench.desktop.main.js:1886:34374)
at VUe.createUntitledNotebookTextModel (vscode-file://vscode-app/c:/Users/victor1.wang/AppData/Local/Programs/Microsoft%20VS%20Code/resources/app/out/vs/workbench/workbench.desktop.main.js:1886:35512)
at Y6e.$tryCreateNotebook (vscode-file://vscode-app/c:/Users/victor1.wang/AppData/Local/Programs/Microsoft%20VS%20Code/resources/app/out/vs/workbench/workbench.desktop.main.js:780:43024)
at Fdt.S (vscode-file://vscode-app/c:/Users/victor1.wang/AppData/Local/Programs/Microsoft%20VS%20Code/resources/app/out/vs/workbench/workbench.desktop.main.js:3145:41680)
at Fdt.Q (vscode-file://vscode-app/c:/Users/victor1.wang/AppData/Local/Programs/Microsoft%20VS%20Code/resources/app/out/vs/workbench/workbench.desktop.main.js:3145:41458)
at Fdt.M (vscode-file://vscode-app/c:/Users/victor1.wang/AppData/Local/Programs/Microsoft%20VS%20Code/resources/app/out/vs/workbench/workbench.desktop.main.js:3145:40546)
at Fdt.L (vscode-file://vscode-app/c:/Users/victor1.wang/AppData/Local/Programs/Microsoft%20VS%20Code/resources/app/out/vs/workbench/workbench.desktop.main.js:3145:39650)
at aee.value (vscode-file://vscode-app/c:/Users/victor1.wang/AppData/Local/Programs/Microsoft%20VS%20Code/resources/app/out/vs/workbench/workbench.desktop.main.js:3145:38444)
at x.B (vscode-file://vscode-app/c:/Users/victor1.wang/AppData/Local/Programs/Microsoft%20VS%20Code/resources/app/out/vs/workbench/workbench.desktop.main.js:30:748)
at x.fire (vscode-file://vscode-app/c:/Users/victor1.wang/AppData/Local/Programs/Microsoft%20VS%20Code/resources/app/out/vs/workbench/workbench.desktop.main.js:30:967) python.startNativeREPL {"value":"ms-python.python","_lower":"ms-python.python"}
I don't have Jupyter extension installed. It was working without that extension too. I tried installing it now but still this error throws.
Terminal REPL works, but native REPL doesn't.
Reactions are currently unavailable
Metadata
Metadata
Labels
area-replbugIssue identified by VS Code Team member as probable bugIssue identified by VS Code Team member as probable bugneeds spikeLabel for issues that need investigation before they can be worked on.Label for issues that need investigation before they can be worked on.
Activity
ChiNoel-osu commentedon Dec 13, 2024
It somehow managed to fix itself today, really had no clue what's going on.
Here's my troubleshooting process:
If I delete all user data and install the Python extension alone, the REPL will work.
But as soon as I turned on setting sync and have all the settings and extensions synced, the REPL stopped working and throws that error message to me again.
I tried doing a clean reinstall of VS Code, same issue.
I tried disabling all extensions except the Python ones, the problem still persists.
I tried installing the jupyter extension, same issue. (REPL was working without this extension too)
I tried downgrading Python extension from v2024.22.0 to v2024.20.0, same issue.
Then I tried going into setting.json, and it doesn't seem to have anything related to REPL. But still I cleared up some grayed out or unnecessary settings. After that the REPL still doesn't work. I also don't think setting.json is causing the issue because REPL was working with this setting.json before.
And then I tried numerous of things including upgrading the Python extension back on and again deleting user data. Then in a session, the native REPL suddenly starts working again. Have no idea why.
Now everything is back to normal. But I think we should leave this issue open because this is quite bizarre.
I was using remote Python REPL (ssh to a server in my LAN) when the issue first happened, but this issue persists locally.
anthonykim1 commentedon Jan 13, 2025
Glad it fixed itself! Let us know if you encounter this again. Thanks