Kannan J
Kannan J
It is just debugging logging to record why direct buffer constructor could not be used in the Netty library. Reg the first stacktrace for example, Netty code has [different control...
Created a PR from the fork provided by nicholashagen in https://github.com/grpc/grpc-java/issues/11150.
Feel free to raise a PR for this.
Netty upgrade requires more exhaustive testing. We will be handling it and work is in progress in https://github.com/grpc/grpc-java/pull/11273
>> Readers are probably also curious about the difference between "accept" and "handle" and which one implementations are expected to override. I think _acceptResolvedAddresses_ is the one implementations should prefer...
Will discuss in next week's API review meeting about _nextAndCompleted_ proposed by the PR instead of the earlier agreed upon name _onNextAndCompleted_.
We have merged PR #11778 with the static method name as nextAndComplete in `StreamObservers`.
I'm not an expert on bazel, but as you are removing the dependency on the grpc repo extension where will com_envoyproxy_protoc_gen_validate and opencensus_proto come from now?
We recently had an [issue](https://github.com/grpc/grpc-java/issues/12109) where ClientCalls.blockingUnaryCall would get stuck waiting if the message framer threw an exception if message size exceeded the maximum outbound message size set on the...
What you mentioned in the above code via comments above ```while (!responseFuture.isDone()) ``` may indeed be the fix when the runnable for the pending call dies abruptly. The handling for...