[grpc-io] Re: grcpio-reflection: Naming inconsistency in source and binary dist on PyPi

It's a behavior in setuptools, you can find more information here: https://github.com/pypa/setuptools/issues/2522 On Wednesday, August 16, 2023 at 3:27:59 AM UTC-7 Patrick Kleindienst wrote: > Hi, > I made the observation that on PyPi, the naming for grpcio-reflection > follows different rules

[grpc-io] Re: Multiple grpc connections using python

Hi, looks like the grpc connection in Flower is one stub created using one channel, grpc Python does support reuse stub for client multiplex, you can refer to our multiplex_client implementation

[grpc-io] Re: grpc libs c++ static linking

>From the error message, linking to abseil library didn't seem to be done correctly. This example (https://github.com/grpc/grpc/blob/master/examples/cpp/helloworld/CMakeLists.txt) would be helpful to understand how it needs to be done. On Thursday, October 5, 2023 at 6:59:17 AM UTC-7 smita

[grpc-io] Re: Accessing Service URL from Server Side

Hi, you should be able to send the service URL using metadata, we have some examples here: https://github.com/grpc/grpc/tree/master/examples/python/metadata. Best, Xuan On Monday, July 17, 2023 at 8:16:23 PM UTC-7 Robert Hardisty wrote: > Hi all, > > For security purposes, we are needing to

[grpc-io] gRFC A72: OpenTelemetry Tracing

I have published a gRFC to support OpenTelemetry Tracing in gRPC. https://github.com/grpc/proposal/pull/389 Comments are welcome! -- You received this message because you are subscribed to the Google Groups "grpc.io" group. To unsubscribe from this group and stop receiving emails from it,

[grpc-io] gRPC and CVE-2023-44487?

Hey! We have tried to find some sort of official clarification on whether/how gRPC is affected by CVE-2023-44487. Is there more information on this somewhere? The closest related thing we could find were recent changes to concurrent streams and RST_STREAM: