fullstorydev / fullstorydev/grpcurl
Feature request: exit stream successfully after receiving N responses
- Dominant language
- Go
- Stars
- 12.8k
- Forks
- 580
- Avg merge
- 1h 8m
- Merged PRs (30d)
- 5
Description
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?
thanks!
Contributor guide
No contributing guide indexed for this repository
Research direction
Start with gRPCurl's existing `-max-time` option and the response-streaming RPC call path. Determine how the CLI reports stream termination, then verify that the requested response count ends successfully in an automated API test suite rather than with `DeadlineExceeded`.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- api, cli
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100