hi, I'm trying to use gRPCurl in some automated API test suite, and I'm not sure what the best way to test response-streaming RPC methods. I would like to call the method, make sure the stream starts, and then gracefully cancel the stream with a success code (assuming everything actually works until that point).
so far, what I've found is the flag -max-time, which limits how long gRPCurl is subscribed to the stream, but then it closes with an ERROR:
Code: DeadlineExceeded
Message: Deadline Exceeded
would it be possible to add an option like -max-response N, which only applies to response-streaming RPCs, and then cancels the stream gracefully once the desired number of responses has been received by gRPCurl?
hi, I'm trying to use gRPCurl in some automated API test suite, and I'm not sure what the best way to test response-streaming RPC methods. I would like to call the method, make sure the stream starts, and then gracefully cancel the stream with a success code (assuming everything actually works until that point).
so far, what I've found is the flag
-max-time, which limits how long gRPCurl is subscribed to the stream, but then it closes with an ERROR:would it be possible to add an option like
-max-response N, which only applies to response-streaming RPCs, and then cancels the stream gracefully once the desired number of responses has been received by gRPCurl?thanks!