I was able to download the tar.gz file of the source and get it to build.
Not sure why git was not working for me.
--
You received this message because you are subscribed to the Google Groups
"grpc.io" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to
I'm not sure why you're unable to checkout the tagged release. It is
available on github (https://github.com/grpc/grpc-java/releases/tag/v1.6.1)
and the command (git clone -b ...) works for me. Is it possible you're
getting a cached version of grpc-java?
Thanks,
Eric
On Mon, Sep 18, 2017 at
I get the same result with 1.6.1. I had tried the 1.6.2 just as a guess
along with a variety of other versions. Sorry that I posted the wrong
command line when I asked the questions. I'm guessing it is a git config
issue, but I don't have a clue on where to look. There is not of lot of
content
It should be v1.6.1, not v1.6.2. See
https://grpc.io/docs/quickstart/java.html, which says to checkout v1.6.1.
Did you find another document saying to use v1.6.2? If so, please let me
know the source for that and I will correct it.
Thanks,
Eric
On Mon, Sep 18, 2017 at 9:26 AM, Jeff Gaer
I encountered a weird behavior in gRPC.
*The symptom* - an active RPC stream is signaled as cancelled on server
side (happens from time to time, I couldn't find any correspondence with
other events in the environment) although the client is active and the
stream shouldn't be closed.
It
Ignore this, it was just a silly bug releasing the stub. Sorry about it.
El lunes, 18 de septiembre de 2017, 11:41:06 (UTC+2), gust...@gmail.com
escribió:
>
> Hi,
>
> Due to some special requirements I need to disconnect the client from the
> server at some point. I destroy the stub and the
Hi,
Has anyone attempted to do a challenge-response / digest
authentication implementation for GRPC? Our current services use a
token and HTTP Digest authentication to prove ownership of the token's
associated secret without passing it over the wire.
>From what I see in the examples, most of the
Hi,
Due to some special requirements I need to disconnect the client from the
server at some point. I destroy the stub and the channel is supposed to
be owned by it but checking with netstat I see the TCP connection to the
server is still ESTABLISHED.
This is the code I have.
