-
Notifications
You must be signed in to change notification settings - Fork 177
Description
Hi. I'm having the same problem with issue #277.
In code written without coroutines, the responseObserver. If an error is raised through onError , retry works normally.
However, if coroutines are included and throw StatusRuntimeException inside it, the retry doesn't work.
I put an example here
This example was created by forking this repository.
If line 27 of io.grpc.examples.helloworld.HelloWorldServer is activated, retry does not work.
only come in once
If line 28 of io.grpc.examples.helloworld.HelloWorldServer is activated, retry work.
come in 5 times
My guess is that it doesn't work because of the value of endOfStream of NettyClientStream.transportHeadersReceived.
false when used with coroutines, but true when used without coroutines.
this is intentional?
thank you.