-
Notifications
You must be signed in to change notification settings - Fork 947
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
ipywidgets stuck at "Loading widget..." in JupyterLab #2623
Comments
What ipywidgets jlab extension do you have installed? |
I knew I was missing one.
|
That's what you have installed? Or you were missing it and now it works great? |
" |
That's what I have. It still doesn't work. I've followed that document you referenced before. |
I would concentrate on making sure the jlab extension is installed and working properly. What other extensions do you have installed? Can you uninstall it, |
That looks okay to me. Are there any other js errors before the ones you posted here that give an indication as to why it isn't loading properly? |
The same issue occurs in both Firefox and Edge. |
The next thing I would do is use the browser debugger to put a breakpoint in the js source for the widget extension to make sure it was loading. Just curious - if you create a completely fresh environment with just lab and widgets installed, does it work? |
I just tried this with the same result.
Where exactly should I put the breakpoint and how will I know if it loads? I'm not too familiar with the js source. I'm assuming it's in here somewhere. |
For what it's worth, I tried installing Jupyter Lab and widgets on two other machines (all through Anaconda) and it results is the same. Here are the steps I've followed to install.
This results in "Loading widget..." and the js errors above for all machines that I've tested. Have I missed something in my installation method? |
I experience the same issue using a fresh conda environment using
Same behavior when using an older version of jupyterlab:
|
I got the same issue with jlab:
These |
I'm still experiencing the same problem. @jasongrout anything we can provide that would be helpful? |
Ah, that's the issue. The console doesn't support widgets, just the notebook. |
So two questions come up for me:
If you (or anyone else) would like to help in these things, we can help you get started. |
Ahhh...that was it. I put it all into a notebook and I can see the widgets properly.
What would this require? I don't have a whole lot of time. I'm in the last year of my Ph.D. so I'm a bit limited in what I can do, but I'd be happy to help provide information if someone else wants to take the lead. |
I switched to notebook and widgets are ok now. |
@christasich - I'll open issues for the two questions I raised above. Glad we got to the bottom of this issue you raised! @xiedidan - this issue is about widgets not working in the console. Can you open another issue, since apparently it is a different problem? From your comment above, it seems it is related to the jlab widgets extension being uninstalled? |
We are already discussing ipywidgets support for the jlab code console at #2370. |
Just to confirm I have the same issue, not working in jupyter lab but working in notebook |
I've been dealing with this problem the past few days. I've scoured past issues and tried all of the different solutions, but none of them have worked for me. I'm running JupyterLab on a remote server running Ubuntu Server 18.04 which I connect to through local port forwarding using Chrome.
Results in "Loading widget..." without actually displaying the widget.
When I inspect the chrome console I see a number of errors like this.
I've tried using my default pip environment and an anaconda environment. Both have resulted in the same thing. When I run the code as an ipynb in standard Jupyter, I am able to see the widget. Any advice here?
Relevant info:
Remote Server: Ubuntu Server 18.04
Local: Windows 10 using Chrome
jupyter core: 4.6.1
jupyter notebook: 6.0.2
jupyter lab: 1.2.3
ipywidgets: 7.5.1
nodejs: 8.10.0
The text was updated successfully, but these errors were encountered: