Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

jupyter notebook interactive window: notebook controller is NOT associated to notebook

See original GitHub issue

Issue Type: Bug

When trying to run any python code in jupyter interactive window I get the following error: notebook controller is NOT associated to notebook: vscode-interactive:Interactive-2.interactive.

This only occurs on a single workspace and happened randomly after workspace had previously been working.

Restarting vscode did not help. I do not have the issue in jupyter notebooks or other workspaces. It was working ok this morning.

Full error:

warn 13:2:40.569: DataScience Error [Error: notebook controller is NOT associated to notebook: vscode-interactive:Interactive-2.interactive
	at Object.createNotebookCellExecution (/home/ubu/.vscode-server/bin/3b889b090b5ad5793f524b5d1d39fda662b96a2a/out/vs/workbench/api/node/extensionHostProcess.js:87:104239)
	at Function.create (/home/ubu/.vscode-server/extensions/ms-toolsai.jupyter-2022.6.1201981810/out/extension.node.js:2:1979904)
	at Function.getOrCreate (/home/ubu/.vscode-server/extensions/ms-toolsai.jupyter-2022.6.1201981810/out/extension.node.js:2:1979775)
	at new v (/home/ubu/.vscode-server/extensions/ms-toolsai.jupyter-2022.6.1201981810/out/extension.node.js:2:1972464)
	at Function.fromCell (/home/ubu/.vscode-server/extensions/ms-toolsai.jupyter-2022.6.1201981810/out/extension.node.js:2:1972734)
	at t.CellExecutionFactory.create (/home/ubu/.vscode-server/extensions/ms-toolsai.jupyter-2022.6.1201981810/out/extension.node.js:2:1971621)
	at t.CellExecutionQueue.queueCell (/home/ubu/.vscode-server/extensions/ms-toolsai.jupyter-2022.6.1201981810/out/extension.node.js:2:1999064)
	at b.executeCell (/home/ubu/.vscode-server/extensions/ms-toolsai.jupyter-2022.6.1201981810/out/extension.node.js:2:2016091)
	at p.executeCell (/home/ubu/.vscode-server/extensions/ms-toolsai.jupyter-2022.6.1201981810/out/extension.node.js:24:154835)
	at x.createExecutionPromise (/home/ubu/.vscode-server/extensions/ms-toolsai.jupyter-2022.6.1201981810/out/extension.node.js:2:1883822)
	at processTicksAndRejections (node:internal/process/task_queues:96:5)]

Extension version: 2022.6.1201981810 VS Code version: Code 1.69.2 (3b889b090b5ad5793f524b5d1d39fda662b96a2a, 2022-07-18T16:12:52.460Z) OS version: Windows_NT x64 10.0.19044 Restricted Mode: No Remote OS version: Linux x64 4.19.128-microsoft-standard Remote OS version: Linux x64 4.19.128-microsoft-standard

System Info

Item	Value
CPUs	Intel® Core™ i7-8565U CPU @ 1.80GHz (8 x 1992)
GPU Status	2d_canvas: enabled canvas_oop_rasterization: disabled_off direct_rendering_display_compositor: disabled_off_ok gpu_compositing: enabled multiple_raster_threads: enabled_on opengl: enabled_on rasterization: enabled raw_draw: disabled_off_ok skia_renderer: enabled_on video_decode: enabled video_encode: enabled vulkan: disabled_off webgl: enabled webgl2: enabled
Load (avg)	undefined
Memory (System)	15.81GB (2.99GB free)
Process Argv	–crash-reporter-id f3a0670e-645e-4838-bcdd-287e0fa3f7ca
Screen Reader	no
VM	0%

Item	Value
Remote	WSL: Ubuntu-20.04
OS	Linux x64 4.19.128-microsoft-standard
CPUs	Intel® Core™ i7-8565U CPU @ 1.80GHz (4 x 1992)
Memory (System)	7.77GB (3.19GB free)
VM	0%

Item	Value
Remote	WSL: Ubuntu-20.04
OS	Linux x64 4.19.128-microsoft-standard
CPUs	Intel® Core™ i7-8565U CPU @ 1.80GHz (4 x 1992)
Memory (System)	7.77GB (3.19GB free)
VM	0%

A/B Experiments

vsliv368cf:30146710
vsreu685:30147344
python383cf:30185419
vspor879:30202332
vspor708:30202333
vspor363:30204092
vslsvsres303:30308271
pythonvspyl392:30443607
vserr242:30382549
pythontb:30283811
vsjup518:30340749
pythonptprofiler:30281270
vshan820:30294714
vstes263cf:30335440
pythondataviewer:30285071
vscod805:30301674
binariesv615:30325510
bridge0708:30335490
bridge0723:30353136
vsaa593:30376534
vsc1dst:30438360
pythonvs932:30410667
wslgetstarted:30449410
vscscmwlcmt:30465135
cppdebug:30492333
pylanb8912cf:30529770
vsclangdf:30486550
841h4636:30531698

Issue Analytics

State:
Created a year ago
Comments:8 (1 by maintainers)

Top GitHub Comments

4reactions

sblandcommented, Aug 10, 2022

I still get this error occasionally and need to switch kernel then switch back again. Mostly happens when opening a new vscode window

2reactions

loftusacommented, Aug 24, 2022

I am getting this error as well. Fresh Ubuntu install.

Top Results From Across the Web

VS Code Interactive notebook - python - Stack Overflow

i can t use #%% anymore as a jupyternotebook cell. Its not marked as one or visuallized in any way. I tried reinstalling...

Working with Jupyter code cells in the Python Interactive window

To select an environment, use the Python: Select Interpreter command from the Command Palette (Ctrl+Shift+P). Once the appropriate environment is activated, ...

Can't restart kernel in VSCode jupyter notebook - VS Code

As the title says, recently notebooks in VSCode does not allow me to press restart kernel or interrupt (greyed out) and running the...

Jupyter Notebook 6.5.2 documentation - Read the Docs

A web application: a browser-based tool for interactive authoring of documents which combine explanatory text, mathematics, computations and their rich media ...

vscode jupyter notebook size limit - You.com | The AI Search ...

Also note that the previous setting used 0 to indicate that the output is unlimited, while the new setting does not. So, if...