[grpc-io] grpc-go balancer behavior when there are no backends

Hi, I had a question about grpc-go's behavior when you use a custom balancer and there are no available backends available. My understanding is with FailFast callopt, the rpc should fail immediately rather then consuming the entire RPC deadline budget. However, that does not seem to be the

[grpc-io] Building grpcio-python without recompiling core files

I was wondering if it was reasonable to have a env variable that affected the `CORE_C_FILES` that is passed into Extension in setup.py (basically something like SKIP_COMPILING_CORE). I’d like to build grpcio python from source and link against grpc_core compiled separately. My understanding of

[grpc-io] grpc.max_metadata_size

Hi, Had 2 questions regarding using "grpc.max_metadata_size" 1. It was not clear to me that `max_metadata_size` takes into account size of "detail" part of response. Can we allow setting "max_metadata_size" to -1 to represent unlimited as with `max_send_message_length` and

[grpc-io] Status of Experimental Interceptor APIs in Go/Python

Hi, My understanding is APIs that are marked as experimental can be removed without notice. I was wondering what the process to promote experimental APIs to stable is and where I can follow along on that. Both the go client side interceptors (which seem mostly unchanged for 1.5 year) and

Re: [grpc-io] [python] Subclassing RpcError

tion chain that inherits from a base class like `RpcCallError(RpcError,Call` makes sense for python and doesn't make the API surface more fragile. Thanks, On Tuesday, February 27, 2018 at 10:30:04 AM UTC-8, Nathaniel Manista wrote: > > On Mon, Feb 26, 2018 at 11:16 AM, aamit via grpc

[grpc-io] [python] Subclassing RpcError

Hi, I had some questions about the api design of RpcError. From what I can tell in docs I should catch RpcError and switch on code (since it's also implicitly a `Call`). A few things frustrate me about this. 1. There are certain codes I'd like to treat one way and certain codes I'd like