Joshua Humphries

FYI, the new formulation, a pointer `*attributes.Attributes`, means that the base balancer will now consider every address a "new address", and recycle every single connection, if the two addresses don't...

@dfawley, thanks for the reply. I filed #3611 for this.

I've thought about this quite a bit, actually. At a former job, my team even wrote something that did just this (though it was bespoke protobuf-based RPC, not gRPC). The...

@wahmedswl, yes. Run `grpcurl -h` and then take a look at the `-protoset-out`. Note, however, that this exports a [`FileDescriptorSet`](https://github.com/protocolbuffers/protobuf/blob/master/src/google/protobuf/descriptor.proto#L57) that is written in the binary protobuf format. It does...

@costela, I'm not sure that would really work. The resulting source would not be compile-able unless it emitted, at a minimum, one file per referenced package. IMO, it would ideally...

This is fixed as of v1.6.1. You can pin grpcurl to a newer version (or even to `@latest`, like you are doing with grpc), or you can pin grpc to...

@laurentvaills, `grpcurl` uses the reflection service correctly. Setting EOS would mean it's issuing two different RPCs, one for each request. However, the reflection service is a bidi streaming endpoint, kind...

@JamesXNelson, why does the scratch base image make this hard to use in Kubernetes? In fact, at FullStory, we do exactly this and even use `grpcurl` in cron jobs to...

`grpcurl` does not implement the HTTP transport or gRPC protocol details. Instead, it relies on the grpc/grpc-go project for that. Looking through proxy-related issues in that project (such as https://github.com/grpc/grpc-go/issues/1446),...

It looks like the Go runtime for gRPC, which is what grpcurl uses under its hood, supports environment variables in a similar fashion as curl and python: HTTP_PROXY, HTTPS_PROXY, and...