Jupyter Notebook Kernel fails to start kernel in Python 3.6

Hello,

Note: I’m working with SSH connection to a remote server; therefore, probably part of the problem is that the connection is not stable as with local work. However, in the previous version of the Jupyter, I did not have those issues.

I updated the visual code to the newest version (the update added a new appearance to the Jupyter notebook and some new features). However, since the update, I have struggled to run the cells. The response of the cell run is not good, and it takes time for it to really run (sometimes it even doesn’t work). In addition, when I stop a cell execution using Keyboard Interrupt, I get an error saying that the code stopped due to Keyboard Interrupt; however, the cell is still executing, and even the time of execution (new feature) is still counting. Even when I try to reset the kernel, it is not responding either (something which always works in the old versions).

To conclude, I can’t explain the issue exactly; however, something has happened since the last update. The Jupyter notebook is not stable as it was before. Therefore, working with SSH conception became almost impossible for me.

Thank you, Ofir

[jeremykawahara]

Have the same overall issue (high lag especially during any sort of IntelliSense/code completion task) starting last night after doing an update. I tried uninstalling/reinstalling the Jupyter extension and different versions of python, but the issue remained.

The workaround I found is to use the old Notebook Editor.

To use the old Notebook Editor, right click the .ipynb notebook, select Open With ..., and choose Jupyter Notebook (custom)

Of note, this Notebook lag seems to be only really noticeable when working on larger projects with multiple notebooks/files. When I start VSCode to only see an empty folder, the new Notebook Editor seems to work fine.

[rchiodo]

Otherwise I’m able to run a cell just fine.