ember h2 client hangs after long running connection dies about http4s HOT 2 OPEN

I tried to distill an example:

https://gist.github.com/nefilim/b47805255431b00866c07f3375fa36ff

I try to simulate the problem by running this on a laptop and then putting it to sleep. Unfortunately it's not quite the same problem, the readLoop does error but so does the writeLoop, those errors does not get propagated.

The connection receives a GoAway which is propagated in the error channel and causes the stream to rebuild, the client recreated and the connection re-established, the desired behaviour.

It seems in my application, the readLoop errors leaving the client in a bad state but no further errors are being propagated to allow clean/recreation .. not quite sure how to simulate that.

from http4s.

When this happens I have two fibers waiting in the same place 🤔

cats.effect.IOFiber@23480178 WAITING
 ├ rethrow$extension @ fs2.Compiler$Target.$anonfun$compile$1(Compiler.scala:157)
 ├ flatMap @ org.http4s.ember.core.h2.H2Stream.getResponse(H2Stream.scala:413)
 ├ main$ @ org.home4s.server.Main$.main(Main.scala:28)
 ╰ main$ @ org.home4s.server.Main$.main(Main.scala:28)

from http4s.