Skip to content
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

Closed
wolfv opened this issue Nov 7, 2023 · 7 comments
Closed

Seeing "unexpected end of file" issues for non-CDN channel #845

wolfv opened this issue Nov 7, 2023 · 7 comments
Labels
locked [bot] locked due to inactivity pending::support indicates user is waiting on support from triage engineers severity::1 blocker; broken functionality with no workaround source::community catch-all for issues filed by community members type::bug describes erroneous operation, use severity::* to classify the type type::support neither a bug nor feature, is really just a user having questions or difficulty somewhere

Comments

@wolfv
Copy link

wolfv commented Nov 7, 2023

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.

2023-11-05T20:13:05.6283585Z   × error sending request for url (https://conda.anaconda.org/robostack-
2023-11-05T20:13:05.6285841Z   │ staging/linux-64/ros-humble-sros2-0.10.4-py310h7c61026_3.tar.bz2):
2023-11-05T20:13:05.6286861Z   │ connection error: unexpected end of file
2023-11-05T20:13:05.6287487Z   ├─▶ connection error: unexpected end of file
2023-11-05T20:13:05.6288023Z   ╰─▶ unexpected end of file
2023-11-05T20:13:05.5862693Z DEBUG validating{path=/home/runner/.cache/rattler/cache/pkgs/ros-humble-sros2-0.10.4-py310h7c61026_3}: rattler::package_cache: downloading https://conda.anaconda.org/robostack-staging/linux-64/ros-humble-sros2-0.10.4-py310h7c61026_3.tar.bz2 to /home/runner/.cache/rattler/cache/pkgs/ros-humble-sros2-0.10.4-py310h7c61026_3
2023-11-05T20:13:05.5872394Z DEBUG validating{path=/home/runner/.cache/rattler/cache/pkgs/ros-humble-sros2-0.10.4-py310h7c61026_3}: rattler_networking::authentication_storage::storage: Unable to retrieve credentials for conda.anaconda.org: Platform secure storage failure: no secret service provider or dbus session found, using fallback credential storage at /home/runner/.rattler/rattler_auth_store.json
2023-11-05T20:13:05.5880002Z  WARN validating{path=/home/runner/.cache/rattler/cache/pkgs/ros-humble-sros2-0.10.4-py310h7c61026_3}: rattler_networking::authentication_storage::fallback_storage: Can't find path for fallback storage on /home/runner/.rattler/rattler_auth_store.json
2023-11-05T20:13:05.5888109Z DEBUG validating{path=/home/runner/.cache/rattler/cache/pkgs/ros-humble-sros2-0.10.4-py310h7c61026_3}: rattler_networking::authentication_storage::storage: Unable to retrieve credentials for *.conda.anaconda.org: Platform secure storage failure: no secret service provider or dbus session found, using fallback credential storage at /home/runner/.rattler/rattler_auth_store.json
2023-11-05T20:13:05.5896238Z  WARN validating{path=/home/runner/.cache/rattler/cache/pkgs/ros-humble-sros2-0.10.4-py310h7c61026_3}: rattler_networking::authentication_storage::fallback_storage: Can't find path for fallback storage on /home/runner/.rattler/rattler_auth_store.json
2023-11-05T20:13:05.5901082Z DEBUG validating{path=/home/runner/.cache/rattler/cache/pkgs/ros-humble-sros2-0.10.4-py310h7c61026_3}: hyper::client::pool: reuse idle connection for ("https", conda.anaconda.org)

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!

@wolfv wolfv added the type::bug describes erroneous operation, use severity::* to classify the type label Nov 7, 2023
@jezdez
Copy link
Member

jezdez commented Nov 7, 2023

Just noting that I've seen this and pinged Anaconda infra folks about it.

@jezdez jezdez added pending::support indicates user is waiting on support from triage engineers severity::1 blocker; broken functionality with no workaround type::support neither a bug nor feature, is really just a user having questions or difficulty somewhere source::community catch-all for issues filed by community members labels Nov 7, 2023
@wolfv
Copy link
Author

wolfv commented Nov 7, 2023

Thanks @jezdez – I think on our end we might try to up the retries.
Another thing to note is that the user mentioned this started to happen only in the last ~3 weeks or so, that's why I thought that it might be related to the infra changes on Anaconda's side.

@jezdez
Copy link
Member

jezdez commented Nov 7, 2023

Thanks @jezdez – I think on our end we might try to up the retries. Another thing to note is that the user mentioned this started to happen only in the last ~3 weeks or so, that's why I thought that it might be related to the infra changes on Anaconda's side.

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.

@rasquith
Copy link

rasquith commented Nov 7, 2023

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.

@barabo
Copy link

barabo commented Nov 7, 2023

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.

(base) canderson@carls-mbp-2 missing_sha256 % wget https://conda.anaconda.org/robostack-staging/linux-64/ros-humble-sros2-0.10.4-py310h7c61026_3.tar.bz2
--2023-11-07 11:23:12--  https://conda.anaconda.org/robostack-staging/linux-64/ros-humble-sros2-0.10.4-py310h7c61026_3.tar.bz2
Resolving conda.anaconda.org (conda.anaconda.org)... 104.17.15.67, 104.17.16.67
Connecting to conda.anaconda.org (conda.anaconda.org)|104.17.15.67|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: unspecified [application/x-tar]
Saving to: ‘ros-humble-sros2-0.10.4-py310h7c61026_3.tar.bz2’

ros-humble-sros2-0.10.4-py310h7c61026_3.tar.     [ <=>                                                                                           ]  58.69K  --.-KB/s    in 0.06s

2023-11-07 11:23:13 (991 KB/s) - ‘ros-humble-sros2-0.10.4-py310h7c61026_3.tar.bz2’ saved [60096]

(base) canderson@carls-mbp-2 missing_sha256 % file ros-humble-sros2-0.10.4-py310h7c61026_3.tar.bz2
ros-humble-sros2-0.10.4-py310h7c61026_3.tar.bz2: bzip2 compressed data, block size = 900k
(base) canderson@carls-mbp-2 missing_sha256 % tar -xjf ros-humble-sros2-0.10.4-py310h7c61026_3.tar.bz2
(base) canderson@carls-mbp-2 missing_sha256 % ll
total 29720
drwxr-xr-x  9 canderson  staff       288 Nov  7 11:24 info
drwxr-xr-x  3 canderson  staff        96 Nov  7 11:24 lib
-rw-r--r--  1 canderson  staff     60096 Feb  6  2023 ros-humble-sros2-0.10.4-py310h7c61026_3.tar.bz2
drwxr-xr-x  4 canderson  staff       128 Nov  7 11:24 share

@jezdez
Copy link
Member

jezdez commented Nov 8, 2023

@barabo I'm interpreting this as a "worksforme" and will close it. @wolfv please let us know if this is still happening.

@jezdez jezdez closed this as completed Nov 8, 2023
@wolfv
Copy link
Author

wolfv commented Nov 8, 2023

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.

@github-actions github-actions bot added the locked [bot] locked due to inactivity label Aug 15, 2024
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Aug 15, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
locked [bot] locked due to inactivity pending::support indicates user is waiting on support from triage engineers severity::1 blocker; broken functionality with no workaround source::community catch-all for issues filed by community members type::bug describes erroneous operation, use severity::* to classify the type type::support neither a bug nor feature, is really just a user having questions or difficulty somewhere
Projects
Archived in project
Development

No branches or pull requests

4 participants