-
-
Notifications
You must be signed in to change notification settings - Fork 512
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
Introductory example doesn't seem to work #415
Comments
You have the JupyterLab extension installed? You can get it with:
|
Ah! I did not have that installed! Thanks!!! |
After installing the extension I am still no seeing any behavior when moving the sliders |
Should maybe mention it again in the Introductory paragraph. |
That's bizarre, does the browser JS console have any errors in it? Could you also try clearing the notebook and reloading the page? |
There is a JS console error:
|
That definitely looks to be responsible for the issue. I've encountered that once before but it went away when I tried again in a new session so I was never able to debug it. I'll try to reproduce using your setup:
For better reproducibility could you tell me if you restarted the JLab server, cleared the notebook and/or reloaded the browser window in between any of those steps? Also lastly, could you confirm you have pyviz_comms 0.7.2? |
I cleared the notebook, restarted the server, and started an incognito browser session:
|
Thanks for looking into this! |
And it's still not working now? |
correct |
No problem, pretty crucial to have first set up going smoothly. Was hoping to release an official announcement blog post next week. Having new users run into this issue immediately is definitely not good. |
Oh one more question, what's the bokeh version? Will assume it's 1.1.0 but you never know. |
|
Ugh, bad news, I can't reproduce it. One last question did you get the packages conda-forge? |
I don't think so, it looks like they all came from defaults. Should I use conda-forge ? |
Ah okay, I'll try a new env from defaults now. Hadn't even realized everything made it onto defaults already. |
i can also build a new env with conda-forge. |
That would be appreciated, thanks for being so patient debugging this with me! |
Yes! It's broken with the packages from defaults, now I just need to figure out why. |
Okay, it seems to be a race condition caused by placing the |
Yup! Moving the call to |
Going to push a minor version of the JupyterLab extension shortly once this is merged: holoviz/pyviz_comms#36 That should fix it when both are in the same cell too. |
Okay, just merged and pushed the updated JupyterLab extension to npm. Would you mind trying to update?
That would be hugely appreciated, so far I've basically written almost all of them with a little editing here or there by @jbednar. They would definitely benefit from a second pair of eyes, even if you just mean the mention of the JLab extension in the introduction. |
@philippjfr I was having the same issue (but with a different notebook). I just reinstalled the updated JupyterLab extension and that seems to have fixed it. I now occasionally get a different error:
But it only happens with the following steps:
Even with the error showing up in the console everything still seems to work. I just thought I'd mention it in case it was related. |
Thanks @sdc50 that's probably an unrelated issue. I think the issue there is that the comm which is responsible for affirming that the frontend has received and processed an event from the backend is not being correctly re-established after reloading the page. Those events are important but not crucial which is why it all appears to work. |
Going to close this since the immediate issue has been addressed. |
Same problem here on Macos Mojave Installed everything from scratch in a new environnment, recent packages. jupyter 1.0.0 py38_7 panel 0.9.3 py_0 pyviz |
Can't reproduce, @phimit do you have the jupyterlab extension installed?
|
Yes I have. If it helps, here's the output from the classic notebook: |
Tested on a linux machine, same conditions (new conda env), same results (both with classic notebook and lab). no hv-extension-comm warning though. The only weird common thing is I had to install matplotlib... I thought it was already in base conda. |
I am having the same issue. pn.interact(fn) does not do anything. I am running panel version 0.9.3 |
Could both of you try to upgrade to 0.9.5? All the packaging issues there should have been resolved now. |
Yes! 0.9.5 fixed the issue. Thank you! |
working now, thanks !
Le mar. 7 avr. 2020 à 16:28, Evan Follis <[email protected]> a
écrit :
… Yes! 0.9.5 fixed the issue. Thank you!
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#415 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/ACCNMCC6KNZVVYIDVWT35CDRLM2BJANCNFSM4HLKHIOA>
.
--
I needed a clue and a drink; one of them I
knew where to find.
|
Great! Thanks for reporting back. |
Setup
Machine: OSX
relevant conda packages:
I naively copied the sine example on the introduction page into a jupyter notebook. The mpl plot appeared however manipulating the widgets produced no outcome:
The text was updated successfully, but these errors were encountered: