Cannot run jupyter kernel using python extension

[simeneide]

I upgraded to the latest code-server today and now the jupyter interactive functionality of the python extension has stopped working. This happens both when I did this using a remote linux machine (docker based on the pytorch 1.9 image), AND when installing code-server on my local macbook. When opening a jupyter notebook a popup with the following information appears:

Command 'Jupyter: Create New Blank Notebook' resulted in an error (command 'jupyter.createnewnotebook' not found)

OS/Web Information

• Web Browser: brave
• Local OS: macOs
• Remote OS: macos
• Remote Architecture:
• code-server --version: 3.11.0 4e8cd09

Steps to Reproduce

On macos (m1):

1. install code-server using install script

2. install python extension (ms-python.python v2021.7.1060902895). This will also install a jupyter extension (ms-toolsai.jupyter v2021.6.832593372)
   

3. Try to open a new jupyter notebook (cmd+shift+p "Jupyter: Create new Blank Notebook")
   
   

The developer console has this error (which is too far in the deep for me to understand):

Expected

A jupyter notebook starts up

Actual

Error message
Command 'Jupyter: Create New Blank Notebook' resulted in an error (command 'jupyter.createnewnotebook' not found)

[jsjoeio]

Thanks for opening the issue! I have never used jupyter notebooks.

Is it possible for you to update the repro steps? What do I need to install or how can I create a new jupyter notebook? Then I can try to reproduce locally and see how we can help you.

Thanks!

[simeneide]

Is it possible for you to update the repro steps? What do I need to install or how can I create a new jupyter notebook? Then I can try to reproduce locally and see how we can help you.

Updated, thanks for coming back to me :) I thought "everyone" had this workflow, because it is such a good one ;)

[jsjoeio]

Thanks @simeneide for working with me (Python/Jupyter noob here). That was very easy to follow and I received the same error as you.

I can't promise when we will get to this but I will add it to the next cycle and label it as high-priority.

Video

(Apologies in advance if I pronounced your name wrong)

Screen.Recording.2021-07-30.at.10.40.27.AM.mov

[balajib-b]

@simeneide the installed jupyter extension facilitates VS Code to interface with jupyter package installed in your env, it doesnt install jupyter notebook to your current environment. I would be happy if you could confirm that the python environment you are using has got jupyter installed.
Open terminal and type "python -m pip list" and check jupyter notebook and its dependent packages are installed. i have been using mixed stack of code server, jupyter, miniconda, pytorch, tensorflow with no issues.
Also requesting you to use latest version of code server.

[simeneide]

Yes, all has and I am also able to start jupyter notebook. Currently using 3.11.0 as that is the latest found in brew (which is used when installing with the script). However, it fails much before it starts connecting to the jupyter kernel (as seen in video), so unsure if this is the problem. Are you not able to reproduce my steps? Alternatively, can you provide a step-by-step of how you get your setup to work?

Also: My steps above are working on 3.10, so something has happened.

[balajib-b]

@simeneide i doubt whether your jupyter installation is in path. there could be few more possibilities pertaining to this error. ping me at ji.balajib[at]gmail.com lets connect remote and debug. Im happy to help

i think this way its going to be quick and then post back solution here. this could help @jsjoeio close few more issues.

[gogobd]

I have the very same problem in 3.11.1 and all previous versions. My last working configuration is code-server-3.9.3-linux-amd64. It would be great if Jupyter Notebooks could be fixed in current versions.

#3776
#3782
#2741

[jsjoeio]

Thanks for the notes @gogobd!

It would be great if Jupyter Notebooks could be fixed in current versions.

It's in the next milestone (3.12) so it will get worked on soon and should come in the next version. We have a couple competing priorities and an off-site this week so I can't promise when but keep an eye out!