-
Notifications
You must be signed in to change notification settings - Fork 295
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
qsl Widget does not render #12885
Comments
This works for me, @matthai please could you enable logging as follows:
|
@DonJayamanne great to see it can work! I switched Jupyter->Logging to verbose, restarted vs code and re-ran the code. I get exactly the same result (attached). Is the "Jupyter output panel" you mention just the area below the cell? |
You can get the output from here
Also note:
|
Here you go |
@DonJayamanne , note that the output of jupyter is in the file |
ms-toolsai-jupyter-insiders.vsix.zip This issue was just identified in another place and i have a fix for this
That should fix it, if not, please comment here #12843 Closing as a duplicate of #12843 |
Hallelujah, @DonJayamanne that worked. Thanks! |
Thank you for your patience and feedback, this fix will be in the next insiders (hence the next relase as well) |
Originally filed by matthai here #12843 (comment)
I have the same problem. My setup is perhaps even simpler.
I am running a fresh install of code-insider locally on an ubuntu 20.04 machine. I am trying to run the qsl package from pip (
pip install qsl
in a fresh env) via the 3 lines of code below, which works on the web-based jupyter. My project has only one root.On the web-based jupyter client, this works fine.
On vscode with ipywidgets 8.0.4 and pre-release versions of jupyter and python extensions, I get:
The contents of the error are very similar to that of @christasich:
[Open Browser Console for more detailed log - Double click to close this message]
Failed to load model class 'MediaLabelerModel' from module 'qslwidgets'
Error: No version of module qslwidgets is registered
at ph.loadClass (https://file+.vscode-resource.vscode-cdn.net/home/matthai/.vscode-insiders/extensions/ms-toolsai.jupyter-renderers-1.0.15/out/node_modules/%40vscode/jupyter-ipywidgets8/dist/ipywidgets.js:2:4099813)
at ph.loadClass (https://file+.vscode-resource.vscode-cdn.net/home/matthai/.vscode-insiders/extensions/ms-toolsai.jupyter-renderers-1.0.15/out/node_modules/%40vscode/jupyter-ipywidgets8/dist/ipywidgets.js:2:4403287)
at ph.loadModelClass (https://file+.vscode-resource.vscode-cdn.net/home/matthai/.vscode-insiders/extensions/ms-toolsai.jupyter-renderers-1.0.15/out/node_modules/%40vscode/jupyter-ipywidgets8/dist/ipywidgets.js:2:4097773)
at ph._make_model (https://file+.vscode-resource.vscode-cdn.net/home/matthai/.vscode-insiders/extensions/ms-toolsai.jupyter-renderers-1.0.15/out/node_modules/%40vscode/jupyter-ipywidgets8/dist/ipywidgets.js:2:4094616)
at ph.new_model (https://file+.vscode-resource.vscode-cdn.net/home/matthai/.vscode-insiders/extensions/ms-toolsai.jupyter-renderers-1.0.15/out/node_modules/%40vscode/jupyter-ipywidgets8/dist/ipywidgets.js:2:4092246)
at ph.handle_comm_open (https://file+.vscode-resource.vscode-cdn.net/home/matthai/.vscode-insiders/extensions/ms-toolsai.jupyter-renderers-1.0.15/out/node_modules/%40vscode/jupyter-ipywidgets8/dist/ipywidgets.js:2:4091039)
at https://file+.vscode-resource.vscode-cdn.net/home/matthai/.vscode-insiders/extensions/ms-toolsai.jupyter-renderers-1.0.15/out/node_modules/%40vscode/jupyter-ipywidgets8/dist/ipywidgets.js:2:4402511
at g._handleCommOpen (https://file+.vscode-resource.vscode-cdn.net/home/matthai/.vscode-insiders/extensions/ms-toolsai.jupyter-2023.2.1000521025/out/webviews/webview-side/ipywidgetsKernel/ipywidgetsKernel.js:2:36493)
at async g._handleMessage (https://file+.vscode-resource.vscode-cdn.net/home/matthai/.vscode-insiders/extensions/ms-toolsai.jupyter-2023.2.1000521025/out/webviews/webview-side/ipywidgetsKernel/ipywidgetsKernel.js:2:38387)
The text was updated successfully, but these errors were encountered: