-
-
Notifications
You must be signed in to change notification settings - Fork 366
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
Empty output (sometimes) for dask=2022.12.1 #1206
Comments
I created the dask=2022.11.1 (working) environment
|
I created the dask=2022.12.1 (not working) environment censusnew with the command:
|
I think the issue is in Datashader rather than HoloViews since I sometimes see no output returned from executing the pure Datashader code above, but I've included the HoloViews code because it's the only way I've found to reliably reproduce the error. |
This is another example of the It is nothing to do with datashader. Datashader doesn't understand anything about sending/receiving data from a web brower, this is all handled by HoloViews. |
Agreed. In the past I believe a problem invoking Datashader did lead to empty responses, but in this case I agree it turns out to have been the jupyter_client 8 issue (jupyter/notebook#6748). |
For this code:
the usual output is:
With dask=2022.11.1 or earlier, the HoloViews plot can be zoomed at will, and rerenders reliably. However, with dask=2022.12.1 (or later, up to the current version 2023.4.0), sometimes there is no output rendered for
ds.tf.shade(agg, how='eq_hist')
, and zooming in and out of the HoloViews plot soon gives various errors that suggest an empty output as well:After those errors start, the plot no longer re-renders.
The text was updated successfully, but these errors were encountered: