Skip to content

iris saver issue (via Dask delayed) with dask==2025.4.0 and 2025.4.1 - fixed in iris=3.12.2 #2716

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

Closed
valeriupredoi opened this issue Apr 23, 2025 · 2 comments · Fixed by #2726
Labels

Comments

@valeriupredoi
Copy link
Contributor

valeriupredoi commented Apr 23, 2025

See failed test, the issue is a change of API after switching to Dask 2025.4.0:

>       self.delayed_completion().compute()
E       AttributeError: 'tuple' object has no attribute 'compute'

I am onto it now 🍺

@valeriupredoi valeriupredoi changed the title iris saver issue (via Dask delayed) iris saver issue (via Dask delayed) with dask==2025.4.0 Apr 23, 2025
@valeriupredoi valeriupredoi changed the title iris saver issue (via Dask delayed) with dask==2025.4.0 iris saver issue (via Dask delayed) with dask==2025.4.0 and 2025.4.1 May 1, 2025
@valeriupredoi
Copy link
Contributor Author

Same issue with dask=2025.4.1

@valeriupredoi valeriupredoi changed the title iris saver issue (via Dask delayed) with dask==2025.4.0 and 2025.4.1 iris saver issue (via Dask delayed) with dask==2025.4.0 and 2025.4.1 - fixed in iris=3.12.2 May 9, 2025
@valeriupredoi
Copy link
Contributor Author

fixed in iris 3.12.2 just released (patch) SciTools/iris#6417

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
1 participant