Joshua Humphries

This is standard JSON encoding for protocol buffers, which is already documented here: https://developers.google.com/protocol-buffers/docs/proto3#json

@larspaulsen, I would file in issue at https://github.com/grpc/grpc-go. There is no intent to write a gRPC-over-HTTP/3 implementation in this repo that is bespoke to `grpcurl` -- we rely on the...

> better to have left the exit code alone so that grpcurl reports back using the grpc standard error codes Not all errors are grpc error codes. The program exits...

I've renamed the issue so it's a doc issue.

What language is the server written in? This appears to be a bug in the server reflection implementation that fails to return the descriptor for this enum.

@MuForum, this is an issue in the grpc-java implementation: https://github.com/grpc/grpc-java/blob/72527708f552036ffcd70923ff12a4b26c9d17d4/services/src/main/java/io/grpc/protobuf/services/ProtoReflectionService.java#L486 It is not adding enums to the set of indexed descriptor names. That means that it cannot answer reflection calls...

@hrpath, can you see what happens on the server? Is the server getting the request to the `ServerReflection` service and then returning an error code? Also, can you provide more...

@shibumi, and what do you see happening server-side? Do you see a failed request? The grpcurl client will try to use the reflection service and will only print this message...

@wwuck, that CVE states: > which (in some situations) allows attackers to bypass access control that is based on IP addresses, because of unexpected octal interpretation There is no such...

Hey, @zellyn! How are you doing? There is already a `max-time` flag. I guess you want it to _cancel_, as opposed to using deadline propagation? Could you instead achieve this...