Open StykMartin opened 10 months ago
Frankly you're paying for Nexus and they're giving two very different messages for the same error. Given how tenuous our ability to detect this already is, I'd strongly push on Nexus fixing this instead of us.
Same issue with Nexus OSS (3.70.1-02) using the new embedded H2 database.
Same issue with Nexus OSS (3.71.0-06) using the new embedded H2 database.
Since the FOSS version is now affected, I think we should address this issue. I'll look into it and provide a patch to fix it.
Glad to hear you're sending a fix to Nexus now that their broken code is open source
Confirming here on Nexus-OSS v3.37.0-12 with embedded H2 db.
It seems like the changed output is since >=v3.71.0, everything before that also supported the OrientDB which is deprecated since then.
@StykMartin any luck on cooking up a patch?
@WatskeBart I have it in my backlog, but since everyone is experiencing the same problem, I will bump it up in priority. I'll cook it this week and see how it goes.
Is there an existing issue for this?
What keywords did you use to search existing issues?
nexus PostgreSQL skip-existing
Please describe why your using this option
Hello maintainers,
We recently migrated from OrientDB to the PostgreSQL database for Nexus Repository Pro (without upgrading Nexus version). We noticed that the --skip-existing option does not work anymore. The problem is that the response from Nexus Repository Pro contains different error messages depending on the DB.
OrientDB
PostgreSQL
Current logic does not cover this behavior https://github.com/pypa/twine/blob/fe1885f2bf896c1852dedea7733a582c5718bbbc/twine/commands/upload.py#L64-L65
Anything else you'd like to mention?
No response