Unable to run Jupyter notebook after update/localhost

Notebook
8

To bring others up to date, Sihyun and I met via an online conference and got things working. Here’s what we did.

As Sihuyn mentioned in his original post, a few days ago things were working fine, then the environment was upgraded. In that upgrade, two (known) issues were introduced.

  1. The jupyter_client version went to 7.0.1 (from 6.1.12). This appears to have introduced an “async-sensitivity” issue that appears to only occur on Windows and can be addressed via the previously referenced issue where AsyncMappingKernelManager is configured. The other workaround is to revert jupyter_client back to 6.1.12, but that’s taking a step backward.
  2. The version of pyzmq was updated from 19 to 20 (sorry, I don’t have the specific version numbers) involved here. The symptoms of this issue is a message like the following immediately following kernel startup and posted to the console window:
Bad file descriptor (bundled\zeromq\src\epoll.cpp:100)

This issue occurs regardless of which version of jupyter_client is in use. We googled the message and came across this recent SO post as the first hit. Following the steps to downgrade pyzmq worked - again regardless of which version of jupyter_client was installed.

We hope this will help others.

3 Likes