You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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 certCaused by:0: error sending request for url (https://s3.amazonaws.com/rds-downloads/rds-ca-2019-root.pem): connection closed before message completed1: connection closed before message completed.
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.
I got this in response to a
move 12 1
command on Zulip:I tried the same command again and it worked.
Possibly same root cause as #332?
The text was updated successfully, but these errors were encountered: