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.

Update to use Bokeh >=2

See original GitHub issue

It appears that the most recent release of bokeh(v2.0.0) included some breaking changes. As a result, the websocket connection is not being established properly:

I am running:

# Name                    Version                   Build  Channel
dask                      2.12.0                     py_0    conda-forge
dask-core                 2.12.0                     py_0    conda-forge
dask-labextension         2.0.0                      py_0    conda-forge
bokeh                     2.0.0            py37hc8dfbb8_0    conda-forge

$ jupyter labextension list
JupyterLab v2.0.1
Known labextensions:
   app dir: /glade/work/abanihi/softwares/miniconda3/share/jupyter/lab
        @jupyter-widgets/jupyterlab-manager v2.0.0  enabled  OK
        @jupyterlab/toc v3.0.0  enabled  OK
        @pyviz/jupyterlab_pyviz v0.9.0  enabled  OK
        dask-labextension v2.0.0  enabled  OK
        jupyterlab-nvdashboard v0.1.9  enabled   X

   The following extension are outdated:
        jupyterlab-nvdashboard

   Consider running "jupyter labextension update --all" to check for updates.

Issue Analytics

State:
Created 4 years ago
Comments:12 (8 by maintainers)

Top GitHub Comments

1reaction

quasibencommented, Mar 30, 2020

Jacob will be out for a bit. @scottyhq I don’t think it would be safe to revert until after bokeh>=2 has been tested and validated to work

0reactions

jsignellcommented, Apr 16, 2020

I just did a mild test of bokeh 2.0.1 with jupyter-server-proxy 1.3.2 and things seem to be working fine. Were there particular failures that people had noticed? Otherwise it seems like we can update the pins.