Hi, Sometimes i have trouble running

kedro jupyter notebook

in VSCode, i get hundreds of these errors when i try to connect: A restart of VSCode helps sometimes, but not always. Any ideas?

[W 21:16:51.228 NotebookApp] 403 GET /api/kernelspecs?1705954611216 (127.0.0.1) 1.060000ms referer=None
[W 21:16:51.228 NotebookApp] Forbidden
[W 21:16:51.228 NotebookApp] 403 GET /api/kernels?1705954611217 (127.0.0.1) 1.110000ms referer=None
[W 21:16:51.228 NotebookApp] Forbidden

Do you have the same problem if you only do

jupyter notebook

? It's mostly a problem with your version of notebooks/jupyter backend. I'd suggest try upgrading it.

There are no problems when running jupyter from other environments. It even runs normally when i use jupyter in the environment where i have installed kedro, its only then i start jupyter from kedro and try to attach a notebook in VSCoden to the server. I am using Anaconda, might that cause problems?

@Christoph Imler does it work if you launch

jupyter

as normal and you use

%load_ext kedro.ipython

on top?

%load_ext kedro.ipython

works, Thanks!

I am glad that solution works. For more visibility, kedro basically run

jupyter notebook

behind the scene with an addition steps that setup a Jupyter kernel. So it shouldn't different from running just

jupyter notebook

. Maybe there are something funky with VScode and Jupyter Kernel, but I don't know exactly what is going wrong. Maybe you can check if you are selecting the correct kernel, it should shows Kedro (<your_project_name>), but the current solution is perfectly fine too!

It is strange. The jupyter server (when started by running

kedro jupyter notebook

) works fine until I connect with a notebook, its only then i get the cascade of errors. I did some tests while i am writing this, and it seems like i have the same errors when i use notebooks in the web browser, but they still run. I am not able to connect to the server in VSCode

Thanks for getting back, to me it sounds like a notebook issue but not a kedro specific one. I have experienced this many times myself and I always just try to re-install the notebook/jupyter version or try to upgrade and it resolves itself.