-
Notifications
You must be signed in to change notification settings - Fork 2.2k
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
poetry publish fails when tool.poetry.source is specified throwing "a repository with name was already added" #9405
Comments
does not reproduce - as expected I see an error about connecting to "my_repo" but no sign of the error that you are reporting
please provide a way to reproduce |
I don't know how else I should reproduce apart from the code above, since it's the one causing the error. If I remove the |
maybe provide a dockerfile in which the error happens, then we should get past any "works on my computer" differences (still works on my computer, though!) |
Just being curious; if you use the "-vvv" flag for publish, is "pytorch-gpu" only being added once? |
For some odd reason, changing the version from "0" to "1" in my |
perhaps you had previously made changes but forgot to hit "save"... well anyway: I guess either provide a repro or close this out, please |
It looks like it is adding |
Where is the poetry config? I have only modified the |
I always forget where it is but it doesn't matter, you can modify and see the contents using the 'poetry config' command. 'poetry config --unset repositories.' should do it I think. |
Description
When releasing some code we have a system which step 1 is to run a unittest. If that passes, the code is published to our internal packages such that we can use them in production.
The code for the unittest/publish is
The issue is that the publish part fails when I want to include pytorch with CUDA, thus I have to specify where to get the CUDA-torch from using the
tool.poetry.source
block.The publish part throws the warning/error
and exists with status 1, making the entire pipeline failing since the package cannot be published.
It seems like the repo specified in
tool.poetry.source
is being added twice, thus failing on the second one.Workarounds
Not in the .toml-file.
The way we work around it later on, is to skip the torch-part completely and then install it manually later on when the package is downloaded (which easily can lead to bugs).
Poetry Installation Method
pip
Operating System
It is run in a docker-container
Poetry Version
1.8.3
Poetry Configuration
Python Sysconfig
No response
Example pyproject.toml
Poetry Runtime Logs
The text was updated successfully, but these errors were encountered: