-
Notifications
You must be signed in to change notification settings - Fork 15
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
Seeing "unexpected end of file" issues for non-CDN channel #845
Comments
Just noting that I've seen this and pinged Anaconda infra folks about it. |
Thanks @jezdez – I think on our end we might try to up the retries. |
Happy to, Wolf! I don't have knowledge about any larger changes, but anecdotally we've seen the conda tests fail with retry issues as well recently, and I wonder if that is related. |
Hi Wolf, thank you very much for reporting this. Currently we're adding a ticket to track this issue. We have not yet implemented the upgrade -- we've been running it through some final testing. Once we implement our upcoming infrastructure upgrade, and if this is issue is still extant, we'll look into prioritizing it. |
The package downloads correctly for me, so maybe this was an intermittent issue. We were having some upstream issues with Cloudflare around the time of the problems, so we can't rule that out.
|
Yeah, I think it was always "working" and it's a random package that fails. But if you didn't make the infrastructure changes yet, idk why it changed. Again, we should probably increase retry limits and backoff time. |
What happened?
Since a while a pixi user sees issues with "unexpected end of file" when downloading packages from
robostack-staging
which is a "non-CDN" channel.I wonder if this could be related to the anaconda.org infrastrucutre changes? Or rate limiting (this is a custom github runner, so has different IP from Github)?
Any hints appreciated!
The text was updated successfully, but these errors were encountered: