One request/stream has its context cancelled, causing the abortStream
The same request/stream also blocks on requestBody.Close
Other requests on the same connection try to acquire the mutex
Is this actually expected/intended behaviour? I.e. do we require that closing the request body should always be non-blocking? If so, I guess we could mitigate by increasing the concurrent connection count, but it feels like we could still hit the deadlock across multiple connections
What did you expect to see?
Other requests be able to make progress whilst the first request is blocked
What did you see instead?
All requests on the same client connection were blocked.
I'm very happy to attempt a fix, but I'm a bit of a novice in this part of the codebase!
The text was updated successfully, but these errors were encountered: