update to xarray 2025.01

[rwegener2]

Would Cryocloud be interested in bumping xarray to the latest version? Official datatree support came out in 2024.10.0, as well as number of bugfixes and improvements since then. We are currently using 2024.7.0.

What was done & how

• xarray version was increased to 2025.01.0 in environment.yml

[github-actions]

👈 Test this PR on Binder

[rwegener2]

/condalock

[rwegener2]

Update: I've been poking around and I have to say I'm a bit confused by this error. The error appears to be that libmamba couldn't solve the environment (critical libmamba Could not solve for environment specs).

When I build the environment with the updated environment.yml manually from the hub, though (using conda env create -f environment.yml) I don't get any conflicts.

Failure step from the logs:

Step 40/55 : RUN TIMEFORMAT='time: %3R' bash -c 'time ${MAMBA_EXE} env update -p ${NB_PYTHON_PREFIX} --file "environment.yml" && time ${MAMBA_EXE} clean --all -f -y && ${MAMBA_EXE} list -p ${NB_PYTHON_PREFIX} '

[weiji14]

Hmm, the error might be something to do with mamba=2? I tried using mamba=1 and it managed to solve the environment.yml file, but when I upgraded to mamba=2.0.6, I got this error locally:

error    libmamba Could not solve for environment specs
    The following package could not be installed
    └─ py-xgboost >=2.1.1 ^cpu.*,2.1.*$ does not exist (perhaps a typo or a missing channel).
critical libmamba Could not solve for environment specs

Looks like a bug with mamba=2 not being able to parse this line

hub-image/environment.yml

Line 86 in a42bab4

- py-xgboost~=2.1.1=cpu*

The cpu* build string glob pattern might be the problematic part. I found this semi-related issue - mamba-org/mamba#3783 that hints at mamba=2 only supporting trailing globs in the version string (i.e. the 2.1.1 part), maybe it doesn't support the build string part (e.g. cpu_pyh1ce2f49_3). See also mamba-org/mamba#3601

[jjerphan]

The problem was related to ~= (see mamba-org/mamba#3647) which just has been fixed, the next version of mamba should resolve the problem.

In the meantime, using py-xgboost >=2.1.1,2.1.* *cpu* works.