Fixlocks

[pp-mo]

Addresses #466

From the actions panel, it appears that the lockfile updates were successfully occurring with the previous py39/py310/py311 version.
But this broke for python 3.12 versions, when python versions were updated.

Also ... Prior to the Python version update, the lockfiles update action seemed to be working, but did not generate PRs as expected.
It may be simply that the target branch "" had been removed, and the actions have permission to update that, but not to (re-)create it. We will check that subsequently ...

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 90.37%. Comparing base (cc0ea12) to head (394566e).

Additional details and impacted files

@@           Coverage Diff           @@
##             main     #470   +/-   ##
=======================================
  Coverage   90.37%   90.37%           
=======================================
  Files           6        6           
  Lines         800      800           
  Branches      105      105           
=======================================
  Hits          723      723           
  Misses         64       64           
  Partials       13       13           

Flag	Coverage Δ
	90.37% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

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

[pp-mo]

Learning notes ...
replacing version matrix ...
[py310, py311, py312] FAIL
[py310] ok
[py310, py311] ok
[py311, py312] FAIL -- py311 cancelled while building lockfile
[py312, py311] FAIL -- py311 cancelled after building lockfile successfully
[py312] simply FAILS

It's not at all clear what is going on :
The tox command for py312-lock works fine locally.
Might be something to do with local Artifactory proxy, but the message is more odd than that :
from (raw) GHA log of the failure ...

.tox create: /home/runner/work/cf-units/cf-units/.tox/.tox
.tox installdeps: tox-conda, tox-run-command, tox >= 3.27.1
py3[12](https://github.com/SciTools/cf-units/actions/runs/10964584112/job/30448507804#step:10:13)-lock create: /home/runner/work/cf-units/cf-units/.tox/py312-lock
ERROR: invocation failed (exit code 1), logfile: /home/runner/work/cf-units/cf-units/.tox/py312-lock/log/py312-lock-0.log
================================== log start ===================================
Channels:
 - conda-forge
Platform: linux-64
Collecting package metadata (repodata.json): ...working... done
Solving environment: ...working... failed

PackagesNotFoundError: The following packages are not available from current channels:
  - python=3.12*

Current channels:
  - https://conda.anaconda.org/conda-forge

To search for alternate channels that may provide the conda package you're looking for, 
  navigate to 
  . . .

[pp-mo]

UPDATE Tues 2024-09-24

After a whole lot of investigation, and multiple dead ends...

It seems that this line was the critical thing
It was, presumably, effectively "pinning" some resources to cause an env in which tox can't successfully create a python 3.12 environment. resulting in log output something like this :

##[group]Run tox -e py312-lock
shell: /usr/bin/bash -l {0}
env:
  ENV_NAME: ci-locks
  CACHE_PERIOD: 2024.19
  INPUT_RUN_POST: true
  CONDA: /home/runner/miniconda3
  CONDA_PKGS_DIR: /home/runner/conda_pkgs_dir
##[endgroup]
.tox create: /home/runner/work/cf-units/cf-units/.tox/.tox
.tox installdeps: tox-conda, tox-run-command, tox >= 3.27.1
py312-lock create: /home/runner/work/cf-units/cf-units/.tox/py312-lock
ERROR: invocation failed (exit code 1), logfile: /home/runner/work/cf-units/cf-units/.tox/py312-lock/log/py312-lock-0.log
================================== log start ===================================
Channels:
 - conda-forge
Platform: linux-64
Collecting package metadata (repodata.json): ...working... done
Solving environment: ...working... failed

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

  - python=3.12*

Current channels:

  - https://conda.anaconda.org/conda-forge

To search for alternate channels that may provide the conda package you're
looking for, navigate to

    https://anaconda.org

and use the search bar at the top of the page.
Note: 'use_only_tar_bz2' is enabled. This might be omitting some
packages from the index. Set this option to 'false' and retry.

Reason

This happened, I think, because conda-forge now delivers only ".conda", instead of ".bz2" files. Hence newer versions of many packages were excluded.
When this control was removed, the failing py312 operation succeeds.

[pp-mo]

Still to do

We should check this for real, after merging this, to demonstrate that an automatically triggered operation (as opposed to manual) can still create the expected PRs.
To do that we will need to temporarily meddle with the cron settings, and once it is proved put them back.