-
Notifications
You must be signed in to change notification settings - Fork 2
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
Update dask version #448
Update dask version #448
Conversation
Pull Request Test Coverage Report for Build 9651968197Details
💛 - Coveralls |
5c55f95
to
6f123a9
Compare
Pull Request Test Coverage Report for Build 9652411782Details
💛 - Coveralls |
Pull Request Test Coverage Report for Build 9652821299Details
💛 - Coveralls |
I saw some threads on xarray about ffill algorithms and maybe they help in not using map_overlap. Putting it here because it's related |
Generally I find the error occuring in the current v1 branch as well |
It depends on the dask version, not our code. Did you check the dask version you were using? |
Yes you are right. The 2024 version seems to cause this. Would be great to use the new optimizer they have but seems we have to figure things on our side. |
a2ba530
to
3ea7dcc
Compare
Pull Request Test Coverage Report for Build 11300006146Details
💛 - Coveralls |
3ea7dcc
to
1aa4a83
Compare
Disabled dataframe.query-planning for now as workaround, to not have to limit the python version anymore. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That seems like the best workaround for now. LGTM
The changes to the dfops in #411 allow to pass the tests with dask2024.6.2, however there are random failures during binning (see dask/dask#11200). This requires further inspection.