Replies: 1 comment 9 replies
-
It would be useful to know what the packages actually were (e.g. the full output of What is the exact (set of) command(s) (such that anyone else can copy-paste them) that you're using to evaluate that the checksums of the installed packages are invalid? I don't know if there is any way to have Pixi revalidate an environment's checksums after it has been created. I think the Pixi developers would need to comment on that.
This is what
I also don't know if there is a way at the command line to tell Pixi to ignore the cache when installing an environment, such that you could not delete the system cache but force there to be a redownload and install. |
Beta Was this translation helpful? Give feedback.
-
|
Can you give two Pixi manifest toml files that when switched between produce the issue you're having? |
Beta Was this translation helpful? Give feedback.
-
[project]
authors = ["Giordon Stark <[email protected]>"]
channels = ["conda-forge"]
description = "Environments for light-roast development"
name = "radiativeDecays"
platforms = ["linux-64", "osx-arm64"]
version = "0.1.0"
[tasks]
hello-world = "python example.py"
preprocess = "python preprocess.py"
cutflows = "python cutflows.py"
[dependencies]
dask-jobqueue = "*"
parse = "*"
atlas-schema = ">=0.2.4"
[feature.dev.dependencies]
tbump = ">=6.7.0"
pylint = "*"
pip-tools = "*"
click = "*"
[feature.dev.tasks]
tbump = "tbump"
generate-lock = "pip-compile --quiet --strip-extras --output-file requirements/light-roast.lock"
lint = "pylint *.py"
[feature.py311.dependencies]
python = "<3.12,>=3.11"
[feature.py312.dependencies]
python = "<3.13,>=3.12"
[feature.py313.dependencies]
python = "<3.14,>=3.13"
[feature.py310.dependencies]
python = "<3.11,>=3.10"
[feature.py39.dependencies]
python = "<3.10,>=3.9"
[feature.af.dependencies]
python = "==3.9.18"
[environments]
dev = ["dev", "py39"]
af = ["af"]
py39 = ["py39"]
py310 = ["py310"]
py311 = ["py311"]
py312 = ["py312"]and [project]
authors = ["Giordon Stark <[email protected]>"]
channels = ["conda-forge"]
description = "Environments for light-roast development"
name = "radiativeDecays"
platforms = ["linux-64", "osx-arm64"]
version = "0.1.0"
[tasks]
hello-world = "python example.py"
preprocess = "python preprocess.py"
cutflows = "python cutflows.py"
[dependencies]
dask-jobqueue = "*"
parse = "*"
atlas-schema = ">=0.2.4"
[feature.dev.dependencies]
tbump = ">=6.7.0"
pylint = "*"
pip-tools = "*"
click = "*"
[feature.dev.tasks]
tbump = "tbump"
generate-lock = "pip-compile --quiet --strip-extras --output-file requirements/light-roast.lock"
lint = "pylint *.py"
[feature.py311.dependencies]
python = "<3.12,>=3.11"
[feature.py312.dependencies]
python = "<3.13,>=3.12"
[feature.py313.dependencies]
python = "<3.14,>=3.13"
[feature.py310.dependencies]
python = "<3.11,>=3.10"
[feature.py39.dependencies]
python = "<3.10,>=3.9"
[feature.af.dependencies]
python = "==3.9.18"
dask-jobqueue = "*"
parse = "*"
[feature.af.pypi-dependencies]
atlas-schema = ">=0.2.4,<0.3"
# the below needed because of https://github.com/prefix-dev/pixi/discussions/3550, see !6
awkward = { git = "git+https://github.com/scikit-hep/awkward.git", rev = "5e3849f385fcd1eab46358ab0ed5f0883bcd113b" }
[environments]
dev = ["dev", "py39"]
af = {features = ["af"], no-default-feature = true}
py39 = ["py39"]
py310 = ["py310"]
py311 = ["py311"]
py312 = ["py312"] |
Beta Was this translation helpful? Give feedback.
-
|
With the first Pixi manifest I get (on UChicago AF, where you were running this) $ pixi list -e af llvmlite
WARN Encountered 1 warning while parsing the manifest:
⚠ The feature 'py313' is defined but not used in any environment
╭─[/home/feickert/workarea/debug/giordon-test/pixi.toml:36:10]
35 │
36 │ [feature.py313.dependencies]
· ─────
37 │ python = "<3.14,>=3.13"
╰────
help: Remove the feature from the manifest or add it to an environment
Environment: af
Package Version Build Size Kind Source
llvmlite 0.43.0 py39hf8b6b1a_1 3.2 MiB conda https://conda.anaconda.org/conda-forge/
$ pixi run --environment af python -c 'import numba; print(numba)'
WARN Encountered 1 warning while parsing the manifest:
⚠ The feature 'py313' is defined but not used in any environment
╭─[/home/feickert/workarea/debug/giordon-test/pixi.toml:36:10]
35 │
36 │ [feature.py313.dependencies]
· ─────
37 │ python = "<3.14,>=3.13"
╰────
help: Remove the feature from the manifest or add it to an environment
<module 'numba' from '/home/feickert/workarea/debug/giordon-test/.pixi/envs/af/lib/python3.9/site-packages/numba/__init__.py'>then switching to the second I get $ pixi list -e af llvmlite
WARN Encountered 1 warning while parsing the manifest:
⚠ The feature 'py313' is defined but not used in any environment
╭─[/home/feickert/workarea/debug/giordon-test/pixi.toml:36:10]
35 │
36 │ [feature.py313.dependencies]
· ─────
37 │ python = "<3.14,>=3.13"
╰────
help: Remove the feature from the manifest or add it to an environment
WARN The package `dask==2024.8.0` does not have an extra named `array`
WARN The package `dask==2024.8.0` does not have an extra named `array`
Environment: af
Package Version Build Size Kind Source
llvmlite 0.43.0 128.2 MiB pypi llvmlite-0.43.0-cp39-cp39-manylinux_2_17_x86_64.manylinux2014_x86_64.wh
$ pixi run --environment af python -c 'import numba; print(numba)'
WARN Encountered 1 warning while parsing the manifest:
⚠ The feature 'py313' is defined but not used in any environment
╭─[/home/feickert/workarea/debug/giordon-test/pixi.toml:36:10]
35 │
36 │ [feature.py313.dependencies]
· ─────
37 │ python = "<3.14,>=3.13"
╰────
help: Remove the feature from the manifest or add it to an environment
<module 'numba' from '/home/feickert/workarea/debug/giordon-test/.pixi/envs/af/lib/python3.9/site-packages/numba/__init__.py'>So things seem to be working as expected. This is with $ pixi self-update
✔ pixi is already up-to-date (version 0.45.0)
$ pixi --version
pixi 0.45.0(I also updated from @kratsg What is the contents of your original |
Beta Was this translation helpful? Give feedback.
-
|
it was commented out to be just a single line and that still crashed because |
Beta Was this translation helpful? Give feedback.
-
|
@kratsg (Ignoring all the For the first ("af" being empty) Pixi manifest $ pixi list --environment af llvmlite
Environment: af
Package Version Build Size Kind Source
llvmlite 0.43.0 py39hf8b6b1a_1 3.2 MiB conda https://conda.anaconda.org/conda-forge/
$ pixi list --environment af numba
Environment: af
Package Version Build Size Kind Source
numba 0.60.0 py39h0320e7d_0 4.1 MiB conda https://conda.anaconda.org/conda-forge/
$ pixi run --environment af python -c 'from atlas_schema.schema import NtupleSchema; print(NtupleSchema)'
<class 'atlas_schema.schema.NtupleSchema'>and then also for the second $ pixi list --environment af llvmlite
Environment: af
Package Version Build Size Kind Source
llvmlite 0.43.0 128.2 MiB pypi llvmlite-0.43.0-cp39-cp39-manylinux_2_17_x86_64.manylinux2014_x86_64.whl
$ pixi list --environment af numba
Environment: af
Package Version Build Size Kind Source
numba 0.60.0 14.3 MiB pypi numba-0.60.0-cp39-cp39-manylinux2014_x86_64.manylinux_2_17_x86_64.whl
$ pixi run --environment af python -c 'from atlas_schema.schema import NtupleSchema; print(NtupleSchema)'
<class 'atlas_schema.schema.NtupleSchema'> |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
When trying to start a pixi project from a toml + lock file, even after running
pixi cleanandpixi reinstalletc multiple times, we always ended up with an error like so:Of particular note was that the
import numbawas crashing out of the box inside thepixi shellenvironment. Digging into the differences between two different users, one who could run this just fine and one who couldn't, I noticed that thellvmliteconda was 12MB on the problematic user's cached area, while thellvmliteconda was 128MB on the passing user's cached area. Confused, I thoughtpixi cleanwould clear out the cache at~/.cache/pixibut even runningpixi cleanstill uses a problematic cache'd file that doesn't even pass the checksum in thepixi.lock.The only solution I found here was the nuclear option:
rm -rf ~/.cacheand then things worked again. It would be nice to understand or find a way to forcepixito check if a package it pulls from the cache is actually valid or not.Beta Was this translation helpful? Give feedback.
All reactions