Re: [grpc-io] Re: Announcing gRPC-Rust

We are still working in earnest on the gRPC-Rust implementation. We expect to have a demo at gRPConf next month and will also be covering it at our upcoming meetup . And if you are interested in tec

[grpc-io] Re: GRPC at APIDays in Paris

Hi Lukasz, Sorry, but unfortunately nobody from the gRPC team will be at APIDays this year. Thank you for the consideration, though, and we hope you have a successful event! Thanks, Doug On Monday, November 13, 2023 at 9:55:59 AM UTC-8 Lukasz Gornicki wrote: > Hi folks, > > Is anyone from g

[grpc-io] Re: gRPC c++ mixed synchronous and asynchronous rpc within one service

[Sorry, forgot to reply-all] There's nothing special about having multiple types of RPCs in a single service. You can see an example of this in the route_guide sample code here: https://github.com/grpc/grpc/tree/master/examples/cpp/route_guide On Thursday, June 29, 2023 at 1:43:14 PM UTC-7 Fra

[grpc-io] Re: Actual Typing Support for grpc-php

Hi Tobias, Is this the same as the request you filed in the github repo, https://github.com/grpc/grpc/issues/33431? If so, we should try to consolidate all discussion there. Thanks, Doug On Thursday, June 29, 2023 at 6:09:07 AM UTC-7 Tobias Grether wrote: > GRPC is a very useful tool that he

[grpc-io] Re: transport.newBufWrite go grpc not releasing memory

Please try enabling keepalive on your server so it will notice the connection was lost: https://pkg.go.dev/google.golang.org/grpc/keepalive#ServerParameters (set Time to something like 30 seconds - 5 minutes depending on your needs) https://pkg.go.dev/google.golang.org/grpc#KeepaliveParams On F

[grpc-io] Re: docker containers connection refused

This sounds like it might be a more generic networking (docker config) problem than a gRPC issue. Are your containers able to reach each other using other operations (e.g. ping)? On Tuesday, May 17, 2022 at 12:06:44 AM UTC-7 fabrizio...@gmail.com wrote: > Hi all, I am setting up an Hyperledger

[grpc-io] Re: controlling GRPC client prefetch

Can you explain your reasoning for wanting to override these settings? BDP and this type of "prefetching" is used to improve performance. Setting these options may not be the best way to solve the problems you are facing, as they will impact all traffic on those connections. It may be prefer

[grpc-io] Re: Managing Shared & Sharing proto definitions & compile packages (go)

This is probably a better question for the protobuf team than the gRPC team. What you described seems like it would work, if my understanding of go.mod is correct. The concern with using generated (pb.go) files from anywhere but a common source location is that the proto library will panic if

[grpc-io] Re: Made golang GRPC non-blocking across AWS multi-regions - High CPU usage impacting performance

On Friday, November 5, 2021 at 4:12:03 AM UTC-7 deepal.t...@gmail.com wrote: > Hi, > > I have implemented Golang grpc on a blockchain for message passing. My > client side and server side code looks as follows: > > 1. Client code > /code that establishes the grpc connection -

[grpc-io] Re: Import "google/api/annotations.proto" was not found or had errors.

If you're having problems with the import being found, this is more likely a generic protobuf usage problem, not really specific to gRPC. Do you have the annotations.proto in your import paths (-I parameter) that you pass on the commandline? On Sunday, September 19, 2021 at 8:30:12 AM UTC-7 Da

[grpc-io] Re: grpc: panic: math/big: mismatched montgomery number lengths

Panics in the standard library should be reported to the go repo: https://github.com/golang/go. This seems deep enough down that it's not a grpc bug or a user error, but I could be mistaken. On Friday, September 17, 2021 at 1:49:43 AM UTC-7 fishe...@gmail.com wrote: > additional remarks: It ha

Re: [grpc-io] Re: Go - Reconnection in bidi streaming RPC communication

On Wednesday, July 14, 2021 at 3:53:40 PM UTC-7 amits...@gmail.com wrote: > Thanks, I am able to understand what you are proposing. With this > approach, when I try to Send() with the stream disconnected, then the > operation will either exit - which is not what I want, or wait for the > recv()

[grpc-io] Re: Go - Reconnection in bidi streaming RPC communication

Only your send _or_ recv path should be recreating the stream. I think I would implement this as: - goroutine performing Send exits on any error (or encounters the error then blocks on a channel until the next step...) - goroutine performing Recv re-creates the Send goroutine if needed (or unb

[grpc-io] Re: question about gRPC-go profiling example

Unfortunately, we had to roll back the change that added in the profiling collection code, and it has not been a priority to find out what was wrong and re-add it. https://github.com/grpc/grpc-go/pull/3378 Note that this feature is intended for inspecting grpc's performance, so shouldn't be v

[grpc-io] Re: how to bind grpc client to specific network interface

Sorry for the very late reply to this question. Yes, this is possible in Go by providing a custom dialer to grpc: https://pkg.go.dev/google.golang.org/grpc#WithContextDialer It would look something like: myDialer := net.Dialer{LocalAddr: } client, err := grpc.Dial(target, , grpc.WithContextD

[grpc-io] Re: Unexpected disconnects

Is there a maximum connection age set on the server (GRPC_ARG_MAX_CONNECTION_AGE_MS)? If so, make sure you have an adequate grace period set (GRPC_ARG_MAX_CONNECTION_AGE_GRACE_MS). Otherwise, enable logging on both the server and the client to determine why the connection is being closed (which

[grpc-io] Re: What happens if server and client are using different proto definitions?

A crash should not occur as a result of a corrupt message (which is how a message with a conflicting encoding appears). On the client side, an error (non-OK grpc status) should occur if this field is set by the server. If a message comes back with a non-OK status, the value read from the mess

[grpc-io] Re: Copyright

Hi Everton, Our copyright license information can be found here: https://github.com/grpc/grpc/blob/master/LICENSE On Friday, October 2, 2020 at 12:52:45 PM UTC-7 Everton Lima Aleixo wrote: > Hello, I am using this lib, and I did not find the correct copyright. > > Could you inform me? > > Than

[grpc-io] gRFC A31: xDS RouteActions Support

All, A proposal was just made to introduce support for xDS RouteActions. Please review the proposal and add any discussion in this thread. https://github.com/grpc/proposal/pull/192 Thanks, Doug Fawley -- You received this message because you are subscribed to the Google Groups "grpc.io" gro

[grpc-io] Re: Performance advice on bi-directional streaming

Sorry for the late reply - in grpc-go, we do batching of sends/receives by default. Setting the Read and Write buffers larger can potentially help, but probably is only useful if your messages are large. In your case, I don't believe there's much else you can do to optimize. Is your primary c