-
-
Notifications
You must be signed in to change notification settings - Fork 526
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
panel 1.4.3 regression: KeyError: 'content' in jupyterlab #6865
Comments
Can't seem to recreate it. Can you check if you have the latest version of pyviz_comms? |
Same issue here, with the latest version of pyviz_comms. How can we help you to reproduce ? |
Looks like issue affects widgets based on jupyter widgets or ipywidgets. Issue is gone after pulling previous environment from git. My venv code sits on its own repo. |
@avivazran what are the package version you are using ? On my side, I have the issue in a venv with (jupyterlab + holoviews[recommended])
|
I think downgrading to 1.4.2 works If I had to guess, I think it might be related to #6818 |
@ahuang I think that the trick is to actually "clean" the notebook. (e.g. |
Actually the trick is to:
|
Background: holoviz/panel#6865
I'm facing the same issue, and the fix suggested above to restart/hard reload does not work for me. The regression is actually from 1.3.8 to 1.4.0, fixing panel version to 1.3.8 resolves the issue for me. |
Nope. 1.4.1 and 1.4.2 work fine. But you must clean the notebook and save it before you reload the tab and restart the kernel. That being said if you don't need some feature from panel 1.4 (or bokeh 3.4) then you are fine with downgrading to 1.3, too |
I also experienced this issue in our Jupyterlab after upgrading its Python environment. |
Yes, this is an urgent regression. Will release 1.4.4 tomorrow. |
ALL software version info
OS: win10
Jupyter Lab Version 4.1.5
bokeh version: 3.4.1
Python version: 3.9.13
Description of expected behavior and the observed behavior
Complete, minimal, self-contained example code that reproduces the issue
Stack traceback and/or browser JavaScript console output
Screenshots or screencasts of the bug in action
The text was updated successfully, but these errors were encountered: