Grpc-go: how to set stream.Recv() timeout?

[xtaci]

how to set stream.Recv() timeout?

[iamqizhao]

You can wait on another goroutine and cancel the stream if the timer fires.

[shafreeck]

I don't think its a good way to rely on a separate goroutine. Why not build the timeout feature in like using context ?

[iamqizhao]

To be clear, the scope of context is rpc (either unary or streaming) instead of a particular message.

[Julio-Guerra]

I'm wondering if this is that clear on the documentation. It really deserves a "Client-Server Synchronization" and "Handling errors" chapters.

[xtaci]

absolutly, doc is not clear enough

[jan4984]

@iamqizhao how to cancel a strem.recv() for bidi-streaming rpc at server side. I not find any stream mehtod.

[MakMukhi]

@jan4984 You can cancel a stream by canceling the context used to create it.

[jan4984]

@MakMukhi no, I mean the server side. The stream is allocated by gRPC framewok.

[nhooyr]

@jan4984 You would return from the goroutine that received the stream.

[jan4984]

@nhooyr but how can I return if I'm blocking at recv() call

[nhooyr]

@jan4984 recv in a different goroutine.

[dfawley]

See also #1229 (esp. this comment and below), which is about Send() deadlines but the same concepts/techniques apply.