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

Error sending request: connection closed before message completed #363

Open
dtolnay opened this issue Feb 24, 2020 · 1 comment
Open

Error sending request: connection closed before message completed #363

dtolnay opened this issue Feb 24, 2020 · 1 comment
Labels
bug Something isn't working

Comments

@dtolnay
Copy link
Member

dtolnay commented Feb 24, 2020

I got this in response to a move 12 1 command on Zulip:

Failed to parse movement, expected move <from> <to>: failed to get RDS cert

Caused by:
0: error sending request for url (https://s3.amazonaws.com/rds-downloads/rds-ca-2019-root.pem): connection closed before message completed
1: connection closed before message completed.

I tried the same command again and it worked.

Possibly same root cause as #332?

@Mark-Simulacrum
Copy link
Member

Hm, so not sure about the other issue, but it looks like for this at least the likely culprit is the problem identified in hyperium/hyper#2136 where S3's timeouts are different from hyper's. Presumably this is trivially reproducible if you send requests "exactly" 20 seconds apart, or so.

I suspect something similar is also the case for CloudFront (which backs the team-api links in #332).

I think the easiest fix here is to just not do keep-alive, I guess? I suppose we should retry in theory... I wonder how e.g. curl and friends deal with this situation.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants