Stream doesn't know that transport is broken about grpc-go HOT 3 CLOSED

I encountered another stream dead lock,

• server stream handler return error
• client waits indefinitely(I could use a timeout contenxt, but it wasn't what I want)

I want to produce it by tests then report it, just not have time yet.

from grpc-go.

I think this is due to the lack of a health checking mechanism to detect the state of transport when no TCP signal (e.g., RST) is generated. The health checking is on our radar but the detailed design has not been fleshed out. For now, you can set a timeout for the entire stream as a workaround. BTW, you can always cancel the rpc via the context binding with the rpc.

For yinhm's question, I have no clue from your simplistic description. Let me know when you have a reproduction.

from grpc-go.

The thread is unresponsive for long time. close it for now. Feel free to reopen if it sustains.

from grpc-go.