-
Notifications
You must be signed in to change notification settings - Fork 179
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
Can't access values of Measurement as property when dask>=2024.11.0
#1656
Comments
tag the issue for tracking dask/distributed#8932 |
Thanks Emma. Love the reproducible example you posted in the dask issue! |
And then I promptly forgot, and spent far too much time today wondering why |
It's particularly bad with numpy2. 2024.11.1 works with numpy1 - but not numpy2, and 2024.11.2 breaks both again. |
There are a bunch of other more or less subtle upstream library issues with numpy2. I just got develop-1.9 CI running with numpy 2 in #1661 - required pinning the MOST recent versions of shapely, netCDF4, and cftime; installing netcdf4 with Dask seems to be the only one affecting numpy 1 though. |
Expected behaviour
Measurement values can be access as property e.g., by
measurement.dtype
.The symptom is that somehow (and somewhere)
Measurement
is casted back to parent classdict
instead ofdatacube.model.Measurement
. Logging parametertype(measurement)
infuse_lazy
shows the different classes information betweendask==2024.10.0
anddask==2024.11.0
Actual behaviour
Emit error when compute
Steps to reproduce the behaviour
Loading multiple scenes with
groupby="solar_day"
Environment information
datacube --version
are you using?1.8.19
sandbox
The text was updated successfully, but these errors were encountered: