Pin dask

[sloosvel]

Description

As discussed in #2607 (comment)
Related to #2607

---

Before you get started

• ☝ Create an issue to discuss what you are going to do

Checklist

It is the responsibility of the author to make sure the pull request is ready to review. The icons indicate whether the item will be subject to the 🛠 Technical or 🧪 Scientific review.

• 🧪 The new functionality is relevant and scientifically sound
• 🛠 This pull request has a descriptive title and labels
• 🛠 Code is written according to the code quality guidelines
• 🧪 and 🛠 Documentation is available
• 🛠 Unit tests have been added
• 🛠 Changes are backward compatible
• 🛠 Any changed dependencies have been added or removed correctly
• 🛠 The list of authors is up to date
• 🛠 All checks below this pull request were successful

---

To help with the number pull requests:

• 🙏 We kindly ask you to review two other open pull requests in this repository

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 95.07%. Comparing base (9aadaca) to head (91b2648).
Report is 1 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #2654   +/-   ##
=======================================
  Coverage   95.06%   95.07%           
=======================================
  Files         255      255           
  Lines       14884    14884           
=======================================
+ Hits        14150    14151    +1     
+ Misses        734      733    -1     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[valeriupredoi]

many thanks @sloosvel - let's pin in the way @bouweandela suggested to allow for some wiggle room for older dasks. Also, could you pls pop the pin in pyroject.toml as well? 🍺

[sloosvel]

That broke the installation:

PackagesNotFoundError: The following packages are not available from current channels:

• dask[version='<2024.8,>=2025']

[valeriupredoi]

eugh silly solver! Shall we just ">=2025" then? @bouweandela @schlunma - what you folks reckon? I found this to be a solid pin, and we get rid of all the crap that came after 2024.8

[valeriupredoi]

we good this way @sloosvel - the env picks up iris==3.11.0 which is fine until iris fix their blocking in 3.11.2 or 3.12 (3.11.1 was released mostly only for the retropin on Dask anyway) 🍺

[sloosvel]

Thanks @valeriupredoi ! By the way, do you know why the tests are failing for Python 3.10?

[valeriupredoi]

Thanks @valeriupredoi ! By the way, do you know why the tests are failing for Python 3.10?

where?

[sloosvel]

In the main branch. A few days ago, the Python 3.12 installation was failing but now it's the Python 3.10 one.

[valeriupredoi]

lemme have a look - nightlies were fine when I checked an hour ago

[valeriupredoi]

ah this one - setup-miniconda is using an old mamba that's causing transient fails, see conda-incubator/setup-miniconda#392 - nothing a rerun can't solve though 😁 That's actually a good point for the release, it could be they won't update the base mamba by then, so expect some of this guff 👍