Open FinleyMcIlwaine opened 3 weeks ago
This solves #139, but uncovered some other uncaught exception output coming from tls
in our stress tests of grapesy
. That output was eliminated with this patch to tls
https://github.com/haskell-tls/hs-tls/pull/477
Instead of
race
ing the background threads and the client, we run them concurrently and check which finishes first. If the background threads finished first, wewait
for the client. If the client finished first, wecancel
the background threads and return.@kazu-yamamoto we also added a case in
sendGoAway
inNetwork.HTTP2.H2.Receiver
so thatGoAwayIsSent
is handled the same asConnectionIsClosed
, which appears to more closely match the behavior of the frame sender. Also, previously ifGoAwayIsSent
happened, it would be wrapped in aBadThingHappen
which would cause the frame sender to rethrow it. Does this change seem acceptable to you?Also, this does not communicate the stream id from a
GOAWAY
to the client if the background threads finish first, but feel free to extend this PR to add that!