-
Notifications
You must be signed in to change notification settings - Fork 62
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
Ignore duplicate requirements #564
Comments
Thanks for the report @q0w! This sounds like a bug -- could you please update your comment to use the bug report template? We use that to reduce the amount of manual maintainer effort needed to triage these kinds of things. |
Updated |
Much appreciated, thank you! From a quick look, this stems from the current "fast path" behavior we have for |
@woodruffw Yep that's correct, this should be fixed with #540. |
@tetsuo-cpp pip-audit v2.5.3 fails now with |
@q0w could you provide the new error message? |
I tried to make a repro, but no success. Also what should I do, if i wanna pip-audit to replace existing version rather than adding new line with fixed version. Its because of provided
|
Hmm, that's because the
It should replace the existing version in the requirements file already. If it's adding a new line for a package that already exists in the requirements file, that's a bug. Do you have a repro? |
I'm going to re-open this so we can address the |
echo "pyjwt==1.7.1" > requirements.in
pip-compile --allow-unsafe --generate-hashes --resolver=backtracking --strip-extras
cat requirements.txt
pip-audit --fix --no-deps -r requirements.txt
cat requirements.txt
It also fails without |
@woodruffw |
new case with pip-audit 2.6.0
It also fails without |
↑ This is a regression bug in 2.6.0 |
Unless I'm misunderstanding, this is not a regression in 2.6.0: it's a known defect from the 2.4 and 2.5 releases. Are you saying that there's a new, different regression in 2.6.0, or are you confirming that the previous bug still exists? |
This example above is working in <2.6.0 |
Gotcha, I understand now: I forgot that we left this open only for the |
Bug description
With using pip-tools workflow for layered requirements pip-audit fails because of duplicate requirements.
Reproduction steps
Expected behavior
No errors
Screenshots and logs
Platform information
pip-audit
version (pip-audit -V
): pip-audit 2.5.2python -V
orpython3 -V
): Python 3.10.10pip
version (pip -V
orpip3 -V
): pip 23.0.1Additional context
The text was updated successfully, but these errors were encountered: