Open emanuel-schmid opened 3 months ago
More failing tests:
Are you sure this is due to dask and not another dependency? I can find nothing related to file locking in the changelog, see https://docs.dask.org/en/stable/changelog.html#v2024-3-0.
Well - this is the full list of changed packages:
package | works | works not |
---|---|---|
coverage | 7.4.4 | 7.4.3 |
dask | 2024.2.1 | 2024.3.0 |
dask-core | 2024.2.1 | 2024.3.0 |
dask-expr | 1.0.1 | |
distributed | 2024.2.1 | 2024.3.0 |
So it could be distributed
I guess. They come together, as for climada, the only package depending on distributed
is dask
.
I haven't checked whether one can install distributed 2024.2 together with dask 2024.3.
(I wouldn't be surprised if the problem disappears with dask 2024.x.y where x is > 3 😁)
dask
2024.3 apparently instroduced a sophisticated locking mechanism which leads to read-only exceptions in various locationsThe current approach to deal with this is to pin
dask
down to 2024.2