Skip to content

Error when pushing: Connection closed before message completed #239

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

Open
ettom opened this issue Apr 27, 2025 · 0 comments · May be fixed by #246
Open

Error when pushing: Connection closed before message completed #239

ettom opened this issue Apr 27, 2025 · 0 comments · May be fixed by #246

Comments

@ettom
Copy link

ettom commented Apr 27, 2025

When pushing many paths at once, attic push often fails with:

Error: error sending request for url (http://127.0.0.1:8180/_api/v1/upload-path)

Caused by:
    0: client error (SendRequest)
    1: connection closed before message completed

This happens regardless of whether a reverse proxy is used or not. It seems especially prevalent if --ignore-upstream-cache-filter is used (probably due to it increasing the amount of uploads dramatically). I can very reliably reproduce it by pushing the ./result of my NixOS build into a fresh cache with --ignore-upstream-cache-filter.

Looks like this is the same issue: hyperium/hyper#2136, mentioned in many other issues and PRs.

I guess in the case of attic, disabling pooling on the client side would be undesirable and it would be better to implement a retry mechanism, at least for this specific error?

@ettom ettom linked a pull request May 19, 2025 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant