grpc-java icon indicating copy to clipboard operation
grpc-java copied to clipboard

The Java gRPC implementation. HTTP/2 based RPC

Results 408 grpc-java issues
Sort by recently updated
recently updated
newest added

### Is your feature request related to a problem? While trying to work with TLS, I was scanning through the current server setup. The NettyServerBuilder configures the port to be...

enhancement

Not in syncContext: https://github.com/grpc/grpc-java/blob/c589441bded0cdf9e321f1d012fb52dd31c172b4/core/src/main/java/io/grpc/internal/ManagedChannelImpl.java#L552 https://github.com/grpc/grpc-java/blob/c589441bded0cdf9e321f1d012fb52dd31c172b4/core/src/main/java/io/grpc/internal/ManagedChannelImpl.java#L280-L282 I also wonder if the behavior is correct, because it seems we are keeping state (`Throttle.tokenCount`) within the service config, which means it is reset...

bug

### Is your feature request related to a problem? Rest is still play an import part in real projects. If the grpc framework could support it, it will be great....

enhancement

Due to the popularity of gRPC, some frameworks or libraries have an integration layer for gRPC. * Armeria: https://line.github.io/armeria/docs/server-grpc * Heldion: https://helidon.io/docs/v2/#/se/grpc/01_introduction * Micronaut: https://micronaut-projects.github.io/micronaut-grpc/latest/guide/index.html Especially, Armeria has its own...

enhancement

1. Implements static authorization server interceptor with end to end tests. 2. Adds support for "v3" HeaderMatcher proto by handling new fields like string_match.

Since v1.37.0, the client channel would panic if receives CDS update with RING_HASH lb policy. ``` SEVERE: [Channel: (xds:///wallet.grpcwallet.io)] Uncaught exception in the SynchronizationContext. Panic! java.lang.NullPointerException: provider at com.google.common.base.Preconditions.checkNotNull(Preconditions.java:910) at...

bug

### What version of gRPC are you using? 1.18.0 ### What did you expect to see? In order to be able to test with JUnit 5 I would like to...

`ManagedChannelBuilder.offloadExecutor()` `NameResolver.Args` `setOffloadExecutor()`/`getOffloadExecutor()` Was originally added in #6238 (was renamed from blockingExecutor)

experimental API

Currently when a service config is supplied, we do not know if things are configured correctly as we desired. Service configs are applied silently. This makes it hard to know...

usability