-
-
Notifications
You must be signed in to change notification settings - Fork 710
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
Deserialization warning with Bokeh 2.1 #3905
Comments
It looks to me that if you remove the |
Is there a new way to align text? |
No there is some bug:
bokeh/bokeh#10181
…On Tuesday, June 16, 2020, Matthew Rocklin ***@***.***> wrote:
Is there a new way to align text?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#3905 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAIHJMBAU4NSNSD34OSW7MLRW6ARXANCNFSM4N7UINNQ>
.
|
OK great. It sounds like the thing for us to do is to sit tight on the Dask side. Correct? |
Yes seems we broke a few eggs with this release unfortunately. |
It's ok, you all make a mean omelet. |
@mrocklin @jsignell Bokeh 2.1.1 is available on PyPI and the bokeh channel on anaconda.org (presumably soon on C-F also) It should resolve this issue (but please test in your actual usage first!) Tangentially: how can we help augment the downstream tests? I plan to raise the visibility of the adivsory downstream tests soon, but that said, they were all still passing even with both issues 2.1 introduced |
Would it make sense for dask to mark some tests as visualization tests and then bokeh could run them on some schedule? Probably released dask + latest bokeh is good enough for testing right? |
@jsignell That's what we do already: https://github.com/bokeh/bokeh/runs/798587187?check_suite_focus=true But evidently not enough already, since it did not catch either of the issues with the 2.1 release. |
Yes sorry should have circled back after the dask dev meeting yesterday. I am going to look over the tests in dask and see if there are any holes in the testing that would be easy to fix. |
Did we wind up resolving this or is this still an issue? |
@jakirkham AFAIK Bokeh 2.1.1 resolved the immediate problem on the Bokeh side, I am not sure if version 2.1 can/was specifically excluded from requirements on the Dask side. Another option would be to set Bokeh 2.1.1 a a new min version which I would certainly endorse 😄 (it is ~18 months old at this point which seem like a lot in dask-time) |
Guessing we would want to update this then @jrbourbeau feel free to point any other spots I've missed :) |
RIght, there's at least that and some docs spots IIRC, and there may be some old version-detection code that could be chucked out. If there's agreement to set 2.1.1 as a new minimum, I am happy to take a comprehensive look and submit a PR. |
Yeah I'd be happy to have the min be 2.1.1 |
Yeah, if bumping the minimum supported version to 2.1.1. will cut down on user pain or maintainer burden, then let's do it |
Thanks Bryan! 😄 |
The dashboard broke under 2.1. It has been resolved in #3904
However, we're still getting a deserialization error like the following:
This comes about from the TaskProgress plot available here:
distributed/distributed/dashboard/components/scheduler.py
Lines 1488 to 1662 in 1d7640b
cc @bryevdv @jsignell
The text was updated successfully, but these errors were encountered: