[grpc-io] quotapool select error cause crash

I am seeing this transient error while using grpc-go (1.10.0-dev) on AIX 7.2 and gcc-go (go version go1.9 gccgo (GCC) 8.0.0 20171205 (experimental) aix/ppc) goroutine 153 [select]: google_golang_org_grpc_transport.get.pN42_google_golang_org_grpc_transport.quotaPool

[grpc-io] [C++] How to simulate GO tls config InsecureSkipVerify

Hi, My C++ Client tries to connect my dev server using TLS but connection keeps failing while checking the dev server certificate. The go version uses the following workaround to skip the verification: grpcOpts := []grpc.DialOption{} creds := credentials.NewTLS({InsecureSkipVerify: *

[grpc-io] Re: End2end testing for gRPC client and server?

My production in this case is a personal GCE VM that I use to upload/download my personal backups. This is just a personal project. Le jeudi 29 mars 2018 22:25:22 UTC+2, ade...@google.com a écrit : > > Hi, Sylvain, > Can you please clarify what you mean by "as close as possible to >

[grpc-io] Re: End2end testing for gRPC client and server?

Hi, Sylvain, Can you please clarify what you mean by "as close as possible to production"? Did you mean close to the OnePlatform environment, going through GFE? Is your backend a Google service? -Adele On Tuesday, March 27, 2018 at 5:27:52 AM UTC-7, Sylvain Le Gall wrote: > > Hi, > > I have

[grpc-io] Re: ALTS outside of GCP

Hi Ruslan, ALTS is not ready for public consumption yet. We could expose ALTS to early access customers. Note that at this point, ALTS is for use inside GCP, such as authentication between two workloads running on GCP or for faster access of Google cloud services on GCP. So far we do not

[grpc-io] Re: [grpc-java] global exception handler on client-side

Point of clarification: Stubs throw exceptions, Calls and Call.Listeners do not. The stubs wrap the calls/listeners and convert Status and Metadata trailers into an exception, but you don't have to. In the code you linked, you can attach a cause to the Status and pass that through in

Re: [grpc-io] Safe to modify message object after yielded to a request/response stream? (Python)

Thanks a lot for responding Nathaniel. In honesty the use case is very slight simplification to a utility generator function. The difference is only a couple of lines, and arguably it would be clearer to explicitly create a new request each time anyway. As you don't guarantee this behaviour,

Re: [grpc-io] Re: Some questions after seeing the Grpc concepts...

On Thu, Mar 29, 2018 at 3:07 AM, Benjamin Krämer wrote: > Hi, nice that you have a look at gRPC. I will answer your questions one by > one. > >> >>- RXJS seems like a perfect library to build into this - specifically >>because it supports returning 1 or a stream of

Re: [grpc-io] Re: Safe to modify message object after yielded to a request/response stream? (Python)

On Thu, Mar 29, 2018 at 5:04 AM, wrote: > Follow up: Would the answer be any different if I was using the > non-blocking API: > > request_iter = my_iter(RequestType(), data) > response_future = my_stub.streaming_request.future(request_iter) > The answer

Re: [grpc-io] Safe to modify message object after yielded to a request/response stream? (Python)

On Thu, Mar 29, 2018 at 4:56 AM, wrote: > Consider the following snippet: > > def my_iter(some_request, extra_data_list): > for item in extra_data_list: > some_request.extra = item > yield some_request >

[grpc-io] Re: Safe to modify message object after yielded to a request/response stream? (Python)

Follow up: Would the answer be any different if I was using the non-blocking API: request_iter = my_iter(RequestType(), data) response_future = my_stub.streaming_request.future(request_iter) -- You received this message because you are subscribed to the Google Groups "grpc.io" group.

[grpc-io] Safe to modify message object after yielded to a request/response stream? (Python)

Consider the following snippet: def my_iter(some_request, extra_data_list): for item in extra_data_list: some_request.extra = item yield some_request some_request.Clear() # ... some time later ... response =

[grpc-io] Re: Some questions after seeing the Grpc concepts...

Hi, nice that you have a look at gRPC. I will answer your questions one by one. > >- RXJS seems like a perfect library to build into this - specifically >because it supports returning 1 or a stream of something. Would also > handle >the timeout case with RX's built in primitives