[grpc-io] Re: Scala gRPC High CPU Utilization

2018-09-10 Thread 'Kos' via grpc.io
Hey Carl, Yup the way you've described it is exactly how I have it setup. private def channelBuilder(address: String): ManagedChannel = { val interceptor = MonitoringClientInterceptor.create(Configuration.allMetrics()) val builder = NettyChannelBuilder .forAddress(address,

[grpc-io] Re: Repeated field is empty on the client side even though it is set on the server side

2018-09-10 Thread jiongjiongfly
Finally it worked after running command below, though the reason for this issue is not clear: killall python Thanks & Best Wishes! Jiongjiong Li On Tuesday, September 11, 2018 at 1:35:29 AM UTC+8, Carl Mastrangelo wrote: > > As a sanity check, are the client and server both using the same

[grpc-io] Re: Repeated field is empty on the client side even though it is set on the server side

2018-09-10 Thread jiongjiongfly
No, both the client and server run in the same anaconda environment and the proto import path are the same. Thanks & Best Wishes! Jiongjiong Li On Tuesday, September 11, 2018 at 1:35:29 AM UTC+8, Carl Mastrangelo wrote: > > As a sanity check, are the client and server both using the same

[grpc-io] [Java] Correct way to terminate call in a ServerInterceptor?

2018-09-10 Thread Jacques
Hello, I have a GRPC protocol I'm working on where I want the ServerInterceptor to terminate the call if I find the metadata invalid. What is the correct way to do it while returning an appropriate status code (permission denied in this case). I'm currently calling call.close() in the

Re: [grpc-io] Seg Fault when calling grpc::ServerInterface::RegisteredAsyncRequest::IssueRequest

2018-09-10 Thread 'Vijay Pai' via grpc.io
In particular, a reason that this is likely to fail out is that your listening port is #1000 , which will only work if you are root. On Monday, September 10, 2018 at 3:35:33 PM UTC-7, Yang Gao wrote: > > The first thing I would check is whether server_ == nullptr after > BuildAndStart. > > On

Re: [grpc-io] Seg Fault when calling grpc::ServerInterface::RegisteredAsyncRequest::IssueRequest

2018-09-10 Thread 'Yang Gao' via grpc.io
The first thing I would check is whether server_ == nullptr after BuildAndStart. On Mon, Sep 10, 2018 at 3:22 PM Alistair Lowe wrote: > Hi guys, > > I'm trying to implement my own gRPC 1.14.2 C++ async server loosely > following the hello world examples, however I receive a segfault when >

[grpc-io] Seg Fault when calling grpc::ServerInterface::RegisteredAsyncRequest::IssueRequest

2018-09-10 Thread Alistair Lowe
Hi guys, I'm trying to implement my own gRPC 1.14.2 C++ async server loosely following the hello world examples, however I receive a segfault when attempting to make an asynchronous request as per the below stack trace: grpc::ServerInterface::RegisteredAsyncRequest::IssueRequest(void*,

[grpc-io] Re: Sending HTTP headers in calls from gRPC PHP client

2018-09-10 Thread tanmad21
Thank you Carl Mastrangelo. That was very helpful! For those who may see this question in the future below is my updated code that works. Notice how setting the $metaData array uses the HTTP2 header key as the array key, and the *header value is and array containing a string of the value*.

[grpc-io] Re: using grpc for push notification

2018-09-10 Thread jonathandotchin
Hello everyone, would anyone have an example in C#/.NET Core? Thanks, Jonathan On Friday, March 16, 2018 at 12:45:31 PM UTC-4, Chaitanya Gangwar wrote: > > > Hi All, > > Previous files got deleted somehow. I am uploading it again. Please use > this link : > > >

[grpc-io] Urgent Order

2018-09-10 Thread Larry Schultz
Hello Am Mr. Larry Schultz .I would like to place an order of from your company to Haiti. kindly email me with your product catalog and also your term of payment. Waiting for your prompt responses. Thank Larry -- You received this message because you are subscribed to the Google Groups

[grpc-io] Re: Best practices and patterns for raising unsolicited events and implement pub/sub?

2018-09-10 Thread jonathandotchin
Hello, have you found an answer to your question? I am also interested in implementing the same system. Thanks, Jonathan On Wednesday, February 8, 2017 at 12:02:25 PM UTC-5, Carl Mastrangelo wrote: > > I am sorry, but I am not that familiar with the c# API, so I can't give > any advice

[grpc-io] Re: Sending HTTP headers in calls from gRPC PHP client

2018-09-10 Thread 'Carl Mastrangelo' via grpc.io
In gRPC, Headers and metadata are the same thing. The formatting for headers should follow normal HTTP rules, such as ignoring case for the header key, and only using the right ascii letters in the value. You can find the rules here:

[grpc-io] Sending HTTP headers in calls from gRPC PHP client

2018-09-10 Thread tanmad21
I am attempting to set some HTTP headers in gRPC client call written in PHP. I cannot find anything specifying how to do this in PHP. From reading docs for other languages I have come to think that headers are specified in the client metadata. However, I can't find anything on how these should

[grpc-io] Re: Using DNS Authority in C# client

2018-09-10 Thread Benjamin Krämer
You would also have to register the resolver. You can have a look at my PR that wasn't merged yet since it's still undecided how the API should look like: https://github.com/grpc/grpc/pull/13639/files -- You received this message because you are subscribed to the Google Groups "grpc.io"

[grpc-io] Re: Using DNS Authority in C# client

2018-09-10 Thread coderharish
Hi Benjamin, sorry for hijacking this old thread, I understood about your point regarding adding own resolver. I have wrote my own resolver in cpp and now I am using `GRPC_DNS_RESOLVER ` to tell the gRPC to pick my resolver. But I gRPC is not picking the resolver, it is always `native`. Do you

[grpc-io] Repeated field is empty on the client side even though it is set on the server side

2018-09-10 Thread jiongjiongfly
The repeated field of protobuf message is always empty on the gRPC client side even though I set it on the gRPC server side. Is there any way to fix this issue? - helloworld.proto file: syntax = "proto3"; package helloworld; // The greeting service definition. service