You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Zeitsperre
changed the title
'xarray.core' has no attribute 'ops' in dask 2025.3.0
'xarray.core' has no attribute 'merge' in dask 2025.3.0
Mar 24, 2025
Zeitsperre
changed the title
'xarray.core' has no attribute 'merge' in dask 2025.3.0
'xarray.core' has no attribute 'merge' wehen running with dask 2025.3.0
Mar 24, 2025
Nope, specifically, when running with dask v2025.3.0, xarray (also v2025.3.0) seems to be acting up.
Zeitsperre
changed the title
'xarray.core' has no attribute 'merge' wehen running with dask 2025.3.0
'xarray.core' has no attribute 'merge' when running with dask 2025.3.0
Mar 24, 2025
Setup Information
Description
I feel like I'm getting deja vu.
It would appear that the latest
dask
isn't playing nicely with our current usages. I'm surprised this wasn't caught by upstream tests.Steps To Reproduce
No response
Additional context
https://github.com/Ouranosinc/xclim/actions/runs/14037153854/job/39297938203
Contribution
Code of Conduct
The text was updated successfully, but these errors were encountered: