[grpc-io] gRPC programming guideline: When to convert status codes?

Dear gRPC developers, We notice that there are many cases gRPC or other status codes are being converted internally through our code analyzer. For example, in https://github.com/grpc/grpc/issues/23775 The error code from ```c // may return GRPC_STATUS_INVALID_ARGUMENT status =

Re: [grpc-io] Re: grpc-python bidirectional streaming delivery status

Thanks. On Wed, Aug 12, 2020 at 12:09 PM 'Richard Belleville' via grpc.io < grpc-io@googlegroups.com> wrote: > gRPC does not handle application-level acknowledgement of receipt of > messages. If you want to do this, you'll have to add it into your protocol. > Your method might look something

[grpc-io] Re: grpc-python bidirectional streaming delivery status

gRPC does not handle application-level acknowledgement of receipt of messages. If you want to do this, you'll have to add it into your protocol. Your method might look something like this: syntax = "proto3"; message MetricRequest { ... } message MetricResponse { oneof payload {

Re: [grpc-io] In gRPC c++, is there a way to get notified when the peer gets disconnected?

There is currently some sort of intermittent bug related to that API: https://github.com/grpc/grpc/issues/18929 On Wed, Aug 12, 2020 at 11:31 AM 'apo...@google.com' via grpc.io < grpc-io@googlegroups.com> wrote: > If you're using the async completion queue based C++ API, then I believe > you can

Re: [grpc-io] In gRPC c++, is there a way to get notified when the peer gets disconnected?

If you're using the async completion queue based C++ API, then I believe you can use the AsyncNotifyWhenDone API for this. See surrounding comments in the linked

[grpc-io] Re: Failed to start grpc server on QNX grpc_combiner_continue_exec_ctx () at grpc_core::ExecCtx::Get()->combiner_data()->active_combiner

There is a similar conversation in https://github.com/grpc/grpc/issues/23714 with more context -- is this the same issue? On Thursday, August 6, 2020 at 10:11:34 PM UTC-7 belanke...@gmail.com wrote: > My code is as simple as below: > > std::string serverAddr = > qaic::qmonInetAll + ":" +

[grpc-io] Study On Rejected Refactorings

Dear grpc developers, As part of a research team from Università della Svizzera italiana (Switzerland) and University of Sannio (Italy), we have analyzed refactoring pull requests in grpc/grpc-java repository and are looking for developers for a short 5-10 min survey

Re: [grpc-io] Building a grpc reverse proxy using client headers

Using a gRPC-based proxy to provide your own logic sounds good and fine. Since you just need headers you could make your own HTTP/2 proxy, but there's nothing wrong with using gRPC as the proxy in my mind. On Thu, Aug 6, 2020 at 1:47 PM wrote: > I couldn't find a lot of documentation on how the

Re: [grpc-io] Uniquely identifying clients in gRPC c++

You can generate a UUID in code, but that will only be valid for the length of deployment. This could be passed in as an option to your client. The best way to identify clients and do it securely is using mTLS (which gRPC does support). On Wed, Aug 12, 2020 at 6:28 AM Sachin Bharadwaj S <

Re: [grpc-io] In gRPC c++, is there a way to get notified when the peer gets disconnected?

Health Checking Protocol: https://grpc.github.io/grpc/cpp/md_doc_health-checking.html On Wed, Aug 12, 2020 at 9:59 AM Mya Pitzeruse wrote: > Let's start with the server case because it's a bit easier. gRPC provides > some built in healthchecking capabilities. Clients watch server health. > When

Re: [grpc-io] In gRPC c++, is there a way to get notified when the peer gets disconnected?

Let's start with the server case because it's a bit easier. gRPC provides some built in healthchecking capabilities. Clients watch server health. When a server goes unhealthy, clients remove them from the pool. gRPC doesn't necessarily surface connection primitives to your server side so it's

[grpc-io] Uniquely identifying clients in gRPC c++

I am implementing gRPC server application and multiple clients are connected to my server and starts to call RPCs. How can the server uniquely identify which client is calling the RPC? Let us assume that server exposes a register RPC and client is implemented in such a way that it calls

[grpc-io] In gRPC c++, is there a way to get notified when the peer gets disconnected?

I have implemented a gRPC server application and multiple clients can connect to it and call RPCs. In the cases of client disconnection or client restarts, I would want to know which client got disconnected so that I can do some cleanup corresponding to that client. Similarly, if the server