Joshua Humphries

@jipperinbham, this is for unary RPCs using the Connect protocol, right? @Alfus, pretty sure this is the same issue you encountered and mentioned to me. We need a way to...

My comment in that PR was > So while it doesn't fully resolve #774, it should help a lot. And yet GitHub decided to auto-close this issue when that PR...

Coincidentally, this would also solve #850 since it provides a way for unary handlers to explicitly set header or trailer metadata, independent of the metadata set on a returned error.

I was thinking a bit more about this: a flag named "simple" may not be the most intuitive way to turn this on. It's not that it's "simpler" than the...

> @jhump should this be added to conformance suite? That's probably a good idea. The well-known types seem to always be causing problems :(

> In summary, I'm looking for ways to attend the interface `grpcurl.DescriptorSource` out of a `protoregistry.GlobalFiles`. Is there a simple way or would it involve deeper changes in `grpcurl`? You...

@mattdowdell, was this in a streaming RPC that you observed this issue? For unary RPCs, the spec that is provided to the handlers is the exact same spec that your...

Ah, my bad. I was incorrectly thinking that the `Peer` was accessed from the `Spec`. (I was accidentally conflating this with a different awkwardness, how the `Query` is accessed from...

@lynxtaa, I suspect the issue is in the server's reflection response. You can test this from the command-line using `grpcurl` itself. * First, you'll need to give gRPC the definition...

So I take it the library you are using parses proto sources, instead of using descriptors compiled by a tool like `protoc` or `buf`? Because that descriptor is indeed wrong....