-
Notifications
You must be signed in to change notification settings - Fork 177
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
connection error while installing environment #2336
Comments
Hey @tmirko, how did you install You can always try with |
Hi @ruben-arts , I've tested it as an installation in WSL ubuntu image as well as starting from https://ghcr.io/prefix-dev/pixi:0.33.0-bookworm docker image. I'm using company's proxy --tls-no-verify doesn't help, same error. |
Could you try |
I also get this periodically. Does retrying cause it to succeed, or at least get to another package before failing? |
Hi @benmoss we also see it just periodically on my machine but on @tmirko it was the whole time We spent today a bit smoke testing and get to some potential scenario where we think that the problem is: private artifactory (with some network security) + slow internet is creating the problem that either some network packages get lost or artifactory stops the connectivity to the client which has open multiple connections to it I don't know if this makes sense at all but by @tmirko connecting to mobile phone (faster internet) solved the problem for now and he was able to install the environment Our questions are:
|
Could this be related to denoland/deno#6197 ? Or at least the underlying issue there with rustls? |
I think @pavelzw and friends also had a number of issues with bad internet / private artifactory / lots of connections at the same time. I think what we can do is:
We'll prioritize these items soon. |
i've also had problems with the exact same setup (artifactory + slowish internet) i debugged some stuff as well with
see https://discord.com/channels/1082332781146800168/1296522386601939055/1296522470559580242 or setup-pixi-error.txt my assumption would be that the slow internet leads to corrupt packages that pixi can't extract, thus an IO error xref #1994 |
what i found interesting in my findings was that the logs only say |
Checks
I have checked that this issue has not already been reported.
I have confirmed this bug exists on the latest version of pixi, using
pixi --version
.Reproducible example
pyproject.toml.txt
Issue description
connection error after executing pixi install command, can't be replicated exactly, sometimes fails on a different conda-forge dependency.
Expected behavior
Successful environment build
The text was updated successfully, but these errors were encountered: