Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Jupyter won't activate with new Insiders

See original GitHub issue

Environment data

VS Code: Version: 1.67.0-insider (user setup) Commit: 345f572e37ca69dc143c9fecb5f851fba9fcce8c Date: 2022-04-05T10:43:52.479Z Electron: 17.3.1 Chromium: 98.0.4758.141 Node.js: 16.13.0 V8: 9.8.177.13-electron.0 OS: Windows_NT x64 10.0.22000

Jupyter Extension version (available under the Extensions sidebar): v2022.3.1000901801
Python Extension version (available under the Extensions sidebar): v2022.4.0
Python and/or Anaconda version: 3.7.9
Type of virtual environment used (N/A | venv | virtualenv | conda | …): n/a
Jupyter server running: Local | Remote |: Local

Computer: System type 64-bit operating system, x64-based processor Edition Windows 11 Enterprise Version 21H2 Installed on ‎10/‎11/‎2021 OS build 22000.556 Experience Windows Feature Experience Pack 1000.22000.556.0

On today’s version of Insiders, Jupyter will not activate because it is using notebook APIs that have been removed by VS Code.

onDidChangeCellMetadata has been removed in favor of onDidChangeNotebookDocument.

The pre-release version of the extension works as expected. I see Jupyter has adopted the new APIs in the pre-release version of the extension, but the Release Version currently does not work.

New APIs: https://github.com/microsoft/vscode/blob/cdb839aa63e04f939bf8587b009621ed2712220e/src/vscode-dts/vscode.proposed.notebookDocumentEvents.d.ts

Console:

[Extension Host] extension activation failed TypeError: s.notebooks.onDidChangeCellMetadata is not a function
  at u.addEventHandlers (c:\Users\allytice\.vscode-insiders\extensions\ms-toolsai.jupyter-2022.3.1000901801\out\extension.js:2:735175)
  at new u (c:\Users\allytice\.vscode-insiders\extensions\ms-toolsai.jupyter-2022.3.1000901801\out\extension.js:2:733840)
  at Object.t.resolveInstance (c:\Users\allytice\.vscode-insiders\extensions\ms-toolsai.jupyter-2022.3.1000901801\out\extension.js:2:2667221)
  at c:\Users\allytice\.vscode-insiders\extensions\ms-toolsai.jupyter-2022.3.1000901801\out\extension.js:2:2669159
  at Array.map (<anonymous>)
  at Object.t.resolveInstance (c:\Users\allytice\.vscode-insiders\extensions\ms-toolsai.jupyter-2022.3.1000901801\out\extension.js:2:2666995)
  at c:\Users\allytice\.vscode-insiders\extensions\ms-toolsai.jupyter-2022.3.1000901801\out\extension.js:2:2669159
  at Object.t.resolve (c:\Users\allytice\.vscode-insiders\extensions\ms-toolsai.jupyter-2022.3.1000901801\out\extension.js:2:2669422)
  at c:\Users\allytice\.vscode-insiders\extensions\ms-toolsai.jupyter-2022.3.1000901801\out\extension.js:2:2652835
  at e._get (c:\Users\allytice\.vscode-insiders\extensions\ms-toolsai.jupyter-2022.3.1000901801\out\extension.js:2:2652601)
  at e.get (c:\Users\allytice\.vscode-insiders\extensions\ms-toolsai.jupyter-2022.3.1000901801\out\extension.js:2:2651244)
  at e.dynamicValue (c:\Users\allytice\.vscode-insiders\extensions\ms-toolsai.jupyter-2022.3.1000901801\out\extension.js:2:2674821)
  at c:\Users\allytice\.vscode-insiders\extensions\ms-toolsai.jupyter-2022.3.1000901801\out\extension.js:2:2668648
  at c (c:\Users\allytice\.vscode-insiders\extensions\ms-toolsai.jupyter-2022.3.1000901801\out\extension.js:2:2667664)
  at c:\Users\allytice\.vscode-insiders\extensions\ms-toolsai.jupyter-2022.3.1000901801\out\extension.js:2:2668588
  at c:\Users\allytice\.vscode-insiders\extensions\ms-toolsai.jupyter-2022.3.1000901801\out\extension.js:2:2668077
  at Array.map (<anonymous>)
  at c:\Users\allytice\.vscode-insiders\extensions\ms-toolsai.jupyter-2022.3.1000901801\out\extension.js:2:2668049
  at Array.map (<anonymous>)
  at Object.t.resolveInstance (c:\Users\allytice\.vscode-insiders\extensions\ms-toolsai.jupyter-2022.3.1000901801\out\extension.js:2:2666995)
  at c:\Users\allytice\.vscode-insiders\extensions\ms-toolsai.jupyter-2022.3.1000901801\out\extension.js:2:2669159
  at Object.t.resolve (c:\Users\allytice\.vscode-insiders\extensions\ms-toolsai.jupyter-2022.3.1000901801\out\extension.js:2:2669422)
  at c:\Users\allytice\.vscode-insiders\extensions\ms-toolsai.jupyter-2022.3.1000901801\out\extension.js:2:2652835
  at e._get (c:\Users\allytice\.vscode-insiders\extensions\ms-toolsai.jupyter-2022.3.1000901801\out\extension.js:2:2652601)
  at e.get (c:\Users\allytice\.vscode-insiders\extensions\ms-toolsai.jupyter-2022.3.1000901801\out\extension.js:2:2651244)
  at a.get (c:\Users\allytice\.vscode-insiders\extensions\ms-toolsai.jupyter-2022.3.1000901801\out\extension.js:2:1109349)
  at c:\Users\allytice\.vscode-insiders\extensions\ms-toolsai.jupyter-2022.3.1000901801\out\extension.js:2:4538183
  at processTicksAndRejections (node:internal/process/task_queues:96:5)
  at c:\Users\allytice\.vscode-insiders\extensions\ms-toolsai.jupyter-2022.3.1000901801\out\extension.js:2:4535892
  at e.activate (c:\Users\allytice\.vscode-insiders\extensions\ms-toolsai.jupyter-2022.3.1000901801\out\extension.js:2:4535127)
  at _activate (c:\Users\allytice\AppData\Local\Programs\Microsoft VS Code Insiders\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:85:8154)
  at _waitForDepsThenActivate (c:\Users\allytice\AppData\Local\Programs\Microsoft VS Code Insiders\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:85:8096)
  at _initialize (c:\Users\allytice\AppData\Local\Programs\Microsoft VS Code Insiders\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:85:7460) (at c:\Users\allytice\.vscode-insiders\extensions\ms-toolsai.jupyter-2022.3.1000901801\out\extension.js:2:4538891)

Expected behaviour

Jupyter activates in VS Code Insiders.

Actual behaviour

Jupyter does not activate.

Steps to reproduce:

Install today’s Insiders. Install latest stable version of Jupyter notebooks. Open a .ipynb file and try to activate extension.

Issue Analytics

State:
Created a year ago
Comments:9 (5 by maintainers)

Top GitHub Comments

1reaction

DonJayamannecommented, Apr 5, 2022

Re-opening as I think we’ll need to fix this, else all users on insiders with stable builds are broken. This is one of the main reasons why we’re warned about using proposed API. We can discuss in stand up whether we need to fix or not, hence opening for now.

0reactions

rchiodocommented, May 10, 2022

Not sure what marketplace you’re looking at, but the latest should be this one (as of me writing this comment)

That’s for stable.

Top Results From Across the Web

What to do when things go wrong - The Jupyter Notebook

If you're using a menu shortcut or Anaconda launcher to start it, try opening a terminal or command prompt and running the command...

python - How does one connect a Jupyter Kernel to VS Code if ...

Open command panel. Mac: CMD+Shift+P PC: CTRL+SHIFT+P · Then search for select Interpreter to start jupyter server then hit enter, it will list ......

Suddenly can't open Jupyter notebooks in VSC Insiders - Reddit

I've been using VSC Insiders to run Jupyter notebooks for months now. As of this morning, I can no longer open a Jupyter...

Multi thread julia kernel (jupyter) fails to start under vscode ...

Turns out that Threads setting cannot be a command line argument in a kernelspec. Must be in the env Dict argument. Andrea_Pagnani ...

Notebooks - Visual Studio Live Share - Microsoft Learn

Before you can start trying out collaborative notebooks, you need to install the ... The neccessary notebook extensions (e.g. Jupyter) ...