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.
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.