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 think that this is a limitation of http2, but I do not know for sure. One potential clue I found during debugging this is that perhaps things go wrong in http2 is we throw an exception in outboundTrailersMaker, but I don't know if that is a red herring or not.
To reproduce this, change clientGlobal in Test.Driver.Dialogue.Execution to always use a single connection, and plenty of test cases will start to fail.
The text was updated successfully, but these errors were encountered:
It's looking like this might have swung to the other extreme. In demo-client.md , section "Automatic reconnect", we describe what should happen to a streaming connection when the server disappears (we expect the call to fail). However, this is not actually happening (anymore?). Instead, we get
I'm seeing that this change in behavior was introduced by #183. At that commit (41b5f2aae727c011921976b68b69e200d9565bba) the demo client started failing with KilledByHttp2ThreadManager rather than CallClosedWithoutTrailers when the server disappears on a streaming connection.
I think that this is a limitation of
http2
, but I do not know for sure. One potential clue I found during debugging this is that perhaps things go wrong inhttp2
is we throw an exception inoutboundTrailersMaker
, but I don't know if that is a red herring or not.To reproduce this, change
clientGlobal
inTest.Driver.Dialogue.Execution
to always use a single connection, and plenty of test cases will start to fail.The text was updated successfully, but these errors were encountered: