grpcurl and server reflection about grpcurl HOT 2 CLOSED

Seems more like server reflection issue rather than grpccurl

from grpcurl.

If your servers are written in Go, it is possible you are running afoul of golang/protobuf#567.

As far as ignoring symbols not required for the call, that is a much bigger change than it sounds. The application uses the protoreflect package to construct descriptors, and that package requires well-formed, linkable descriptors. The ability to "partially process" descriptors is reasonable, such that descriptors do "lazy" linking, deferring the work until necessary (and achieve the effect you are requesting). But that is a significant undertaking -- effectively a re-write of descriptor linking and symbol resolution, which would also require different types and thus different abstractions (e.g. new interfaces) to provide compatibility with the existing types and their existing "eager" implementation.

from grpcurl.