-
-
Notifications
You must be signed in to change notification settings - Fork 402
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
If using multiple package indices, an unresolved host error prevents the subsequent indices from being tried #1945
If using multiple package indices, an unresolved host error prevents the subsequent indices from being tried #1945
Comments
…uests to get package url - Specificall, this resolves pdm-project/pdm#1945 which was caused by an unknown host name due to not having a DNS entry.
I don't agree, LinkCollectionError will be silent unless |
That is a good point, but that means that there isn't really any way to resolve the situation that I have run into. Because the DNS is different locally vs ci, the project will have to choose one or the other for the source, since having both will break things. I am trying to see if we can get the DNS issue consistent, but it seems to me that others might run into a similar issue... Would it be possible to add a parameter for sources that allows them to be skipped if they fail? |
@frostming So, in order to get around this, I figured that I could use the global pdm config to set the repository, and just have different config in ci vs local. This works, but I did notice that it seems that Line 64 in 1638e62
So, basically, it seems that it is not possible to set a true |
Fixes #1945 Signed-off-by: Frost Ming <me@frostming.com>
Make sure you run commands with
-v
flag before pasting the output.Steps to reproduce
I have a situation where the DNS for an internal pypi index is different between my local laptop and the ci node we use to build packages (I think it is probably the same EC2 instance, but the DNS is just different). This makes dev/ci a bit challenging, since
pdm
fails with an error onpdm install
if the dns for a source cannot be resolved, even if multiple sources have been specified. Here is an example of the setup that I am trying:Each source works individually for either CI on Jenkins or locally on my laptop.
Actual behavior
pdm
fails due to a exception raised when it is unable to resolve the DNS for one of the sources:<name 1>
.Expected behavior
Instead of failing with an exception, it seems like it would be better to catch the error, log it, and then move on to the next source (if available).
Environment Information
The text was updated successfully, but these errors were encountered: