No such comm target registered: jupyter.widget.control

[Dabbrivia]

only when using the python3-radcad kernel the following error message appears in jupyter stderr:

[I 18:23:38.821 NotebookApp] Kernel started: 6d4a1706-b4c2-4273-91d5-2ae345c56627, name: python3-radcad
[IPKernelApp] ERROR | No such comm target registered: jupyter.widget.control
[IPKernelApp] WARNING | No such comm: 1f650824-a671-48d5-97d4-b3c93ce824c4

if a vanilla kernel is chosen (ipykernel python3) this error does not appear.

[Dabbrivia]

I have tried to fix it using the suggestions jupyter-widgets/ipywidgets#1720 but to no avail.

[Dabbrivia]

Hm, I have installed the virtual environment anew and now the same error appears for all kernels. So this seems unrelated to the radcad kernel. I will close this here.

[Dabbrivia]

So the culprit seems to be jupyter-book or some of it's dependencies.
To reproduce

poetry new testenv
cd testenv
poetry shell
pip install cadCAD radcad cadCAD_tools jupyterlab 
jupyter lab

the jupyter lab starts with no error message

pip install jupyter-book
jupyter lab

now this error appears:

[IPKernelApp] ERROR | No such comm target registered: jupyter.widget.control
[IPKernelApp] WARNING | No such comm: e5c13e62-2a11-4dd5-aafb-979d90f9af26

Same problem appears when ipywidgets is installed.

jupyter-book is in the requirements list for the cadlabs project template so maybe this is indeed relevant.

[BenSchZA]

Hey @Dabbrivia ! Thanks for detailing the issue here - I'm sure it will prove useful for anyone who has a similar issue. It doesn't seem specific to radCAD, but rather the dependencies and specific development environment as you pointed out.

[utkonos]

@Dabbrivia @BenSchZA This isn't related to jupyter-book it appears to be related to ipywidgets. Unfortunately, someone added a report of this issue to a much older, unrelated issue here:

jupyter-widgets/ipywidgets#2257

It looks like it got the attention of a maintainer, but there hasn't been any activity on that issue for a while after the request for more information. I've provided a step-by-step way to reproduce this error over there.

[BenSchZA]

Closing this issue, thanks for the context above! It will remain in closed issues as a reference for future devs that run into it.