[grpc-io] Re: Regarding the protoc version coming with protobuf-compiler and grpcio-tools

2024-05-28 Thread 'Eugene Ostroukhov' via grpc.io
One should use the protoc and protobuf that comes with the gRPC version they use. Source files generated by a specific protoc version may require specific protobuf API that would make them incompatible with a different protobuf version. On Sunday, May 26, 2024 at 8:48:16 PM UTC-7 Ramana Reddy w

[grpc-io] Re: grpc 1.62 performance regression compared with 1.55

2024-05-28 Thread 'Eugene Ostroukhov' via grpc.io
Please file an issue on GitHub for the team to take a look. On Wednesday, May 22, 2024 at 9:10:15 PM UTC-7 Yunhao Bai wrote: > Recently, w

[grpc-io] Re: Is it safe to modify the const request passed by grpc framework?

2024-05-30 Thread 'Eugene Ostroukhov' via grpc.io
It is not advisable to do that. gRPC is very careful with the memory so the memory location in that const request may be pointing to some internal buffer and might be overridden or freed when the code does not expect that. On Wednesday, May 29, 2024 at 10:32:09 PM UTC-7 amandee...@gmail.com wrot

[grpc-io] Re: Is it safe to modify the const request passed by grpc framework?

2024-06-03 Thread 'Eugene Ostroukhov' via grpc.io
I can not provide a quick example for that but I do know for a fact that internally gRPC is trying to avoid memory copies so some of those string views are pointing to internal data structures. I believe I've at least seen it with initial metadata. Please do not cast the constness away. On Frid

[grpc-io] Re: Grpc c++ server compiling using was

2024-06-11 Thread 'Eugene Ostroukhov' via grpc.io
Please provide the error message. I am not sure if this was attempted before (or what you are trying to achieve)... On Monday, June 10, 2024 at 8:25:27 PM UTC-7 revathi anbumalar wrote: > I have a sample c++ grpc server application which works fine. Now I am > trying to compile it using Wasi (e

Re: [grpc-io] Re: Grpc c++ server compiling using was

2024-06-14 Thread 'Eugene Ostroukhov' via grpc.io
gRPC does not support WASI platform. On Thu, Jun 13, 2024 at 3:50 AM revathi anbumalar wrote: > Getting few errors like below for the sample when compiling using emcc > > 453 | #error "Could not auto-detect platform" > 543 | #error Must define exactly one of GPR_GCC_ATOMIC, GPR_GCC_SYNC, > GPR_

[grpc-io] Re: GRPC C++: Pre-fork worker model

2024-07-12 Thread 'Eugene Ostroukhov' via grpc.io
gRPC is not designed for this scenario. gRPC closes all file descriptors before forking so the connections would not be available in the client. This is explicit expectation and is covered with this test case - https://github.com/grpc/grpc/blob/master/test/cpp/end2end/client_fork_test.cc On Mond

[grpc-io] Re: custom polling interval for pull

2022-11-23 Thread 'Eugene Ostroukhov' via grpc.io
I would like to suggest checking this for the specific cloud products. On Tuesday, November 22, 2022 at 12:25:46 AM UTC-8 b.phan...@gmail.com wrote: > Experts, > > Is it possible to tune the internal polling interval for pull services? I > am trying to use cloud pub/sub on GCP and want to know

[grpc-io] Re: ServerContext deconstruct coredump

2022-11-23 Thread 'Eugene Ostroukhov' via grpc.io
Please provide more details. On Monday, November 21, 2022 at 7:08:41 PM UTC-8 daimin...@gmail.com wrote: > > [image: WeChatWorkScreenshot_324eb9ea-2b13-4351-b9ae-50011b1304d6.png] > Did anyone who ever encountered this problem, ask for help > -- You received this message because you are subscri

[grpc-io] Re: Exception on connection

2023-04-12 Thread 'Eugene Ostroukhov' via grpc.io
Please review this guide on gRPC authentication: https://grpc.io/docs/guides/auth/ More information on your setup (i.e. what authentication method you are using, gRPC version, etc) would also be helpful. On Wednesday, April 12, 2023 at 2:08:06 AM UTC-7 Jens Melzer wrote: > After setting up a c

[grpc-io] Re: GRPC NOT STARTED

2023-06-21 Thread 'Eugene Ostroukhov' via grpc.io
Are you publishing the ports as expected by the Docker? See https://docs.docker.com/network/ Please provide more information, e.g. your Dockerfile. On Wednesday, June 21, 2023 at 5:34:34 AM UTC-7 Priyam Arya wrote: > Hi team, > > I am using grpc in the Springboot service. When I am starting the

[grpc-io] Re: gRPC - HTTP protocol validation

2023-06-21 Thread 'Eugene Ostroukhov' via grpc.io
What do you mean by protocol validation? On Friday, June 16, 2023 at 5:11:13 AM UTC-7 Arup Maitra wrote: > Hi, > > I am using a gRPC client and gRPC service and everything is working fine. > However I am trying to validate the Http protocol whether properly HTTP/2 > is using or not, so I am usi

[grpc-io] Re: How to enable TLS authentification in Python

2023-06-21 Thread 'Eugene Ostroukhov' via grpc.io
This is not specific to gRPC. I believe outside web sites like https://serverfault.com/questions/17061/generate-self-signed-ssl-certificate-for-apache can be helpful to understand how to generate pem files. On Tuesday, June 20, 2023 at 5:44:46 AM UTC-7 Luca Maurelli wrote: > I'm new to gRPC a

Re: [grpc-io] Re: GRPC NOT STARTED

2023-06-21 Thread 'Eugene Ostroukhov' via grpc.io
.server.port=8008 > > Running my service with > > sudo docker run -d -p 5402:5402 -p 8007:8007 > > > > > On Wed, Jun 21, 2023 at 11:27 PM 'Eugene Ostroukhov' via grpc.io < > grpc-io@googlegroups.com> wrote: > >> Are you publishing the ports as expe

Re: [grpc-io] Re: GRPC NOT STARTED

2023-06-21 Thread &#x27;Eugene Ostroukhov&#x27; via grpc.io
e, >>> >>> server.port=5402 >>> grpc.server.port=8008 >>> >>> Running my service with >>> >>> sudo docker run -d -p 5402:5402 -p 8007:8007 >>> >>> >>> >>> >>> On Wed, Jun 21, 2023 at 11:27 PM &

[grpc-io] gRFC A71: xDS fallback

2023-08-24 Thread &#x27;Eugene Ostroukhov&#x27; via grpc.io
https://github.com/grpc/proposal/pull/386 details a proposal to implement support for fallback when xDS control plane is not available. Comments and suggestions are welcome. -- You received this message because you are subscribed to the Google Groups "grpc.io" group. To unsubscribe from this g

[grpc-io] Re: Affected versions - CVE-2023-32731

2023-08-30 Thread &#x27;Eugene Ostroukhov&#x27; via grpc.io
This does not seem to apply to gRPC Java as that one is a separate codebase. 1.48 does not seem to have this specific vulnerability it is no longer maintained and will not receive fixes if any new issues are discovered. We would recommend you to switch to a more current gRPC version. On Tuesday

[grpc-io] Re: Can't compile gRPC 1.57.0

2023-08-30 Thread &#x27;Eugene Ostroukhov&#x27; via grpc.io
Please make sure to run `git submodule update --recursive` when pulling from gRPC GitHub repository. On Friday, August 25, 2023 at 4:16:24 PM UTC-7 apo...@google.com wrote: > I'm not sure exactly how, but my suspicion is that you are somehow picking > up an old `ares.h` on your include path. >

Re: [grpc-io] Re: Affected versions - CVE-2023-32731

2023-08-30 Thread &#x27;Eugene Ostroukhov&#x27; via grpc.io
Yes. Python module calls into C code. On Wed, Aug 30, 2023 at 11:48 AM Josef Cacek wrote: > Thank you for the reply, Eugene. > Is the response also valid for the Python grpcio module? > Regards, > -- Josef > > st 30. 8. 2023 v 19:15 odesílatel 'Eugene Ostroukhov

[grpc-io] Re: grpc c++ write log to file

2023-11-07 Thread &#x27;Eugene Ostroukhov&#x27; via grpc.io
I am not sure what request_id you mean. You may get textual representation of the request or response by calling the DebugString message. ABSL log also has built-in support for proto messages: ::envoy::service::discovery::v3::DiscoveryRequest req; req.add_resource_names("aaa"); gpr_log(GPR_ERROR

[grpc-io] Re: grpc C++ unit testing rpc services

2023-11-07 Thread &#x27;Eugene Ostroukhov&#x27; via grpc.io
This is an open-ended question and depends a lot on the granularity of the tests you want. We have unit tests that test the service class directly. Sometimes we start a service on a background thread and then connect to it from the test. There is no premade test harness that I know of. This is

Re: [grpc-io] Re: grpc C++ unit testing rpc services

2023-11-07 Thread &#x27;Eugene Ostroukhov&#x27; via grpc.io
I would advise against mocking internal interfaces. That may make the tests increasingly brittle when you update gRPC version. Also, it may reduce the test coverage. On Tue, Nov 7, 2023 at 12:48 PM smita deshpande wrote: > I am thinking of mocking the interface grpc::internal:: > ServerAsyncStre

[grpc-io] Re: grpc::Channel::Channel

2024-01-16 Thread &#x27;Eugene Ostroukhov&#x27; via grpc.io
Please provide more information, including the command lines you are using, gRPC version and such. On Monday, January 8, 2024 at 10:35:07 AM UTC-8 Jackieson Liaoo wrote: > I use these two command lines to generate pb.h and pb.cc files > respectively. This is the content of my proto file. [image

[grpc-io] Re: grpc cross compilation issue

2024-01-16 Thread &#x27;Eugene Ostroukhov&#x27; via grpc.io
Please use a newer gRPC version that is compatible with a desired protobuf version. On Tuesday, January 9, 2024 at 9:13:56 AM UTC-8 Uthayakumar Murugan wrote: > Hi > i am using grpc version 1.38.0 ,In this grpc package protobuf version is > 3.15.8 ,i have updated the protobuf version to 3.18.0

[grpc-io] gRPC-Core Release 1.62.0

2024-02-22 Thread &#x27;Eugene Ostroukhov&#x27; via grpc.io
This is 1.62.0(guardian ) release announcement for gRPC-Core and the wrapped languages C++, C#, Objective-C, Python, PHP and Ruby. Latest release notes are here . Core [metadata] Al

[grpc-io] Re: Building grpc on MacOS (15.2)

2025-01-14 Thread &#x27;Eugene Ostroukhov&#x27; via grpc.io
I would suggest asking this on ABSL repository: https://github.com/abseil/abseil-cpp/ On Monday, January 13, 2025 at 7:25:36 AM UTC-8 Ron Grosberg wrote: > Hi, it might be a very silly question, but I can't get around this: > We have a C++ application that was written for Ubuntu. I am trying to

[grpc-io] gRPC-Core Release 1.71.0

2025-03-12 Thread &#x27;Eugene Ostroukhov&#x27; via grpc.io
This is 1.71.0(gears ) release announcement for gRPC-Core and the wrapped languages C++, C#, Objective-C, Python, PHP and Ruby. Latest release notes are here . Core - [CallAttem