-
Notifications
You must be signed in to change notification settings - Fork 306
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
--skip-existing seems not to work with some Nexus version #693
Comments
|
Thanks for the quick answer and I definitely agree with the point on repositories not breaking things. Given that the boolean evaluation is lazy the above code would only impact uploads returning a 400 and not having "updating asset" in reason. For my example, time seems to be ok:
--> around 1e-06 seconds on a correct macbook (not very precise and more powerful that a ci machine indeed) 400 + "bad request" is obviously not enough. twine/twine/commands/upload.py Line 51 in b5fa957
|
I mean we might as ewll |
This is fixed by #694. |
Environment
Issue
The
--skip-existing
flag that is supposed to ignore upload errors when a package is already existing in the repository is not working with my configuration:Nexus Repository OSS: 3.25.1-04
.When trying to upload a package that is already existing, I had a look at what's happening in the
skip_upload
function:twine/twine/commands/upload.py
Line 30 in b5fa957
status
,reason
andtext
values are obtained from the responseIn my case, I have:
status:
400
reason:
bad request
text:
The
skip_upload
function is looking for a400
and"updating assets"
in thereason
string, but in my case"updating assets"
is not inreason
but intext
.I would suggest to change
twine/twine/commands/upload.py
Line 49 in b5fa957
with something like
Steps to Reproduce
I have not tried to replicate with a local nexus repo.
The text was updated successfully, but these errors were encountered: