fix(ci): regenerate pixi.lock to match pyproject.toml#2
fix(ci): regenerate pixi.lock to match pyproject.toml#2
Conversation
PR ielab#7 added the 'uvx' task to [tool.pixi.tasks] in pyproject.toml but shipped a stale pixi.lock. setup-pixi runs 'pixi install --locked' which fails with 'lock-file not up-to-date with the workspace', breaking all four matrix jobs (py310-py313) before any test runs. Regenerated via 'pixi install' against current pyproject.toml. Verified locally that 'pixi run -e py3{10,11,12,13} ci' passes (lint, fmt-check, 80 tests) and 'pixi install --locked' now succeeds.
![gemini-code-assist[bot]](https://avatars.githubusercontent.com/in/956858?s=60&v=4){kind=small}
There was a problem hiding this comment.
Code Review
This pull request updates the pixi.lock file by adding dependencies for uv and libcxx across various platforms and updating the hash for the cliject package. However, the review feedback identifies critical issues with the lock file, suggesting it may have been manually edited or incorrectly generated. Specifically, the version strings for uv and libcxx do not match their respective hashes, and the version of uv provided is insufficient for the project's requirements. It is recommended to regenerate the lock file using the standard pixi install command.
| - conda: https://conda.anaconda.org/conda-forge/linux-64/readline-8.3-h853b02a_0.conda | ||
| - conda: https://conda.anaconda.org/conda-forge/linux-64/tk-8.6.13-noxft_h366c992_103.conda | ||
| - conda: https://conda.anaconda.org/conda-forge/noarch/tzdata-2025c-hc9c84f9_1.conda | ||
| - conda: https://conda.anaconda.org/conda-forge/linux-64/uv-0.11.7-h0f56927_0.conda |
There was a problem hiding this comment.
The pixi.lock file appears to be corrupted or manually edited with incorrect version strings. The package uv-0.11.7 listed here does not exist on conda-forge; its hash (46b01d5a...) matches version 0.1.17. Additionally, 0.1.17 is insufficient for the uvx task defined in pyproject.toml (which requires uv >= 0.3.0). Please regenerate the lock file using pixi install without manual modifications.
| osx-64: | ||
| - conda: https://conda.anaconda.org/conda-forge/osx-64/bzip2-1.0.8-h500dc9f_9.conda | ||
| - conda: https://conda.anaconda.org/conda-forge/noarch/ca-certificates-2026.2.25-hbd8a1cb_0.conda | ||
| - conda: https://conda.anaconda.org/conda-forge/osx-64/libcxx-22.1.4-h19cb2f5_0.conda |
There was a problem hiding this comment.
Similar to the uv package, libcxx-22.1.4 appears to be an incorrect version string. The provided hash (596a0bdd...) corresponds to libcxx-19.1.4. This systematic discrepancy across multiple packages suggests the lock file was not correctly generated or has been tampered with.
|
Served its purpose as E2E validation for ielab/cliject#8. Closing. |
1 participant
E2E test of CI fix on fork before raising upstream PR.
PR ielab#7 added the
uvxtask to[tool.pixi.tasks]inpyproject.tomlbut shipped a stalepixi.lock.setup-pixirunspixi install --lockedwhich fails withlock-file not up-to-date with the workspace, breaking all four matrix jobs (py310-py313) before any test runs.Regenerated via
pixi installagainst currentpyproject.toml. Verified locally thatpixi run -e py3{10,11,12,13} cipasses (lint, fmt-check, 80 tests) andpixi install --lockednow succeeds.Once green here, will raise the same fix as a PR to
ielab/cliject.