-
Notifications
You must be signed in to change notification settings - Fork 204
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Pixi lock file is always out-of-date after introducing pypi-dependencies
#1217
Comments
So I found out why this is. Note if you run with I think because this project is using a nested structure to include multiple projects this problem occurs.
Editables and requirements are kind of disjunct in pypi world. So this may cause issues. I'll need to investigate as bit further. |
I'm getting similar issue when trying to use my env:
This basically ends changing lockfile every time when I use it. It can also be a bit inconvenient when sharing .lock in git repository. I think that using
I guess tensorflow is not doing easy work for this env |
@niemiaszek Thanks for you example. We've been looking for a smaller example this helps! If you find any smaller reproducible examples please let us know! |
Sure, I will try to come with some examples. As I started to use Pixi daily, I will have more chance to experiment with "minimal not working examples". I will give it a chance over the weekend |
@Hofer-Julian I can confirm that your issue is fixed by #1251 @niemiaszek I am pretty sure your issue is solved by #1253 (not entirely sure because your example doesnt include a lock). |
I confirm that the lockfile is declared as up to date, but an issue still remains. Specifically, it seems to always get overwritten with no changes despite pixi declaring that it is up to date. This, for example, makes direnv trigger on every action. |
Can you provide the pixi.toml? |
My OS is Ubuntu 24.04 if that's important. I have the latest pixi (0.24.2). The toml is what I got after pixi init
pixi add python
pixi add "black @ https://github.com/psf/[email protected] [project]
name = "pixi_test"
version = "0.1.0"
description = "Add a short description here"
authors = ["Anton Akhmerov <[email protected]>"]
channels = ["conda-forge"]
platforms = ["linux-64"]
[tasks]
[dependencies]
python = ">=3.12.4,<3.13"
[pypi-dependencies]
black = { git = "https://github.com/psf/black.git", rev = "24.4.2" } I added
I then observe that direnv runs pixi initialization on every action in the terminal. |
You are using sdists instead of wheels. I experienced something similar in #1046 |
Actually, that does look like a 🐛!
This environment is considered unsatified while it shouldnt be. |
Ok @akhmerov I've just noticed, I think you are trying to use a tag as a revision, we don't support tags (yet). I'm thinking that's the problem. |
Thank you for the explanation. I confirm that switching to a revision instead of a tag works. |
I'm also seeing this one in https://github.com/sourmash-bio/sourmash To reproduce on a specific commit with the issue (current
Edit
And allow direnv to run: direnv run
What caught my attention was the line:
what is the index missing? pixi info:
|
@luizirber You've got an interesting situation. You perfectly mimicked the [project.dependencies] with the |
@luizirber That will be fixed in: #1862 |
Fixed with #1862 |
Checks
I have checked that this issue has not already been reported.
I have confirmed this bug exists on the latest version of pixi, using
pixi --version
.Reproducible example
git clone -b pixi-install --single-branch https://github.com/Deltares/Ribasim.git cd Ribasim pixi install pixi install --locked
The last command will fail with
× lock-file not up-to-date with the project
I can reproduce this behavior on Linux and Windows machines.
Issue description
Something seems to be fishy with our pixi setup after @Jingru923 moved to using
pypi-dependencies
: Deltares/Ribasim#1400Pixi always seem to consider the lock file out-of-date. I would love to make a smaller reproducer, but many other projects use
pypi-dependencies
just fine, and I don't see what makes the Ribasim setup special.Expected behavior
Pixi should be able to update the lockfile in a way, that it afterwards is able to recognice that the lockfile is up-to-date.
The text was updated successfully, but these errors were encountered: