-
-
Notifications
You must be signed in to change notification settings - Fork 285
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
Spurious lockfile sync errors when writing to a known pip log file #2568
Labels
Comments
Is this just a matter of setting |
No, its here: Lines 79 to 96 in d94fa6a
Lines 113 to 119 in d94fa6a
I handle the multi-target case correctly (say you sepcify 2 --complete-platforms), but not the single target common case. |
jsirois
added a commit
to jsirois/pex
that referenced
this issue
Oct 23, 2024
Previously, when only 1 resolve target was specified, a `--pip-log` would be re-used which would append the current Pip log outout with the prior output. For a normal PEX build, this was potentially confusing, but for a `pex3 lock` command it could lead to errors since the log is used to generate the lock. Fixes pex-tool#2568
Merged
jsirois
added a commit
that referenced
this issue
Oct 25, 2024
Previously, when only 1 resolve target was specified, a `--pip-log` would be re-used which would append the current Pip log outout with the prior output. For a normal PEX build, this was potentially confusing, but for a `pex3 lock` command it could lead to errors since the log is used to generate the lock. Fixes #2568
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Reproduction:
This doesn't happen if
--pip-log
is not set.My understanding of what is happening: when setting
--pip-log pip.log
pex appends to the file. So presumably pex is trying to parse lines from previous pip runs, and is confused when it sees data for requirements that aren't in the current set of input requirements.The text was updated successfully, but these errors were encountered: