mirror of
https://github.com/serai-dex/serai.git
synced 2025-12-08 20:29:23 +00:00
e1c07d89e0
I don't like blindly retrying in the Monero library. The amount of errors, which weren't present with reqwest (well, the error rate was the same, yet due to a distinct bug this code fixed), demand we do *something* though. The trace log shows hyper is erroring with 0 bytes of the response read. My guess is it's somehow a closed connection? A connection pool would detect this and have created a new connection (as this does, except once finding out there's an issue). While we should be able to detect this with `ready()`, we do call ready and it claims no error. We also can successfully write which makes this... a mess. Hopefully, it either actually works as intended, yet it at least requires two consecutive errors which should be much less frequent.