Joshua Humphries

@neild, FWIW, I took a look at things guarded by `flags.ProtoLegacy`, and marshaling/unmarshaling is already guarded. So I think a useful change here would be to just remove this [one...

@WillAbides, I don't intend to fix this issue in this repo. This repo does not attempt to generate descriptors that will match the output of `protoc` byte-for-byte. You can now...

Closing this issue as "won't fix". This capability, to match `protoc` output byte-for-byte, actually exists in protoparse's replacement: https://github.com/bufbuild/protocompile.

I still need to run `apidiff` on this to make sure that I haven't accidentally broken the exported API. I don't want this to be a v2 of these packages:...

@sharooksubana, is the self-signed certificate being used by the server? Or were you using it as a client certificate? If you are using it as a client certificate, you need...

It is unclear from the description if you are using client cert authentication. If so, you need to use `-cert` and `-key` args. If you are doing that and the...

@hanyouqing, no progress. For one, this is not possible using the gRPC runtime for Go -- the ability to use different hostnames for the TLS servername vs. the authority was...

This change can be made independently. `grpcurl` uses `github.com/jhump/protoreflect/grpcreflect` under the hood, and that package [now supports v1 of server reflection](https://github.com/jhump/protoreflect/pull/535). With the latest version of that package, if using...

> **chrome network tab** > > Why t1 and t2 are HTTP headers? @visortelle, this is actually part of the gRPC spec. If an operation returns an immediate error (so...

BTW, new conformance test cases were added specifically around unknown enum values in the JSON format: https://github.com/protocolbuffers/protobuf/pull/9534