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

The Go language implementation of gRPC. HTTP/2 based RPC

Results 594 grpc-go issues
Sort by recently updated
recently updated
newest added

NOTE: if you are reporting is a potential security vulnerability or a crash, please follow our CVE process at https://github.com/grpc/proposal/blob/master/P4-grpc-cve-process.md instead of filing an issue here. Please see the FAQ...

Status: Requires Reporter Clarification
Type: Bug
Area: RPC Features

As far as I can tell, the `passthrough:///` scheme does not appear to be documented anywhere. It is needed in order to properly use the bufconn package. It is mentioned...

Type: Documentation
Area: Documentation

## Description Currently, the ordering of server-side stats events is not explicitly documented in the `stats.Handler` interface, nor verified through tests. This can lead to confusion for users implementing stats...

Status: Help Wanted
P2
Type: Bug
Area: Server

https://github.com/envoyproxy/go-control-plane/issues/431 is a bug in the go-control-plane implementation that results in the server not sending resources in certain cases. We have some workaround in some tests for this. Once the...

P2
Type: Testing
Status: Blocked
Area: xDS

Presently not all LB policies handle endpoints, some still read `resolver.Addresses`. These LB policies will need to be changed incrementally to handle endpoints correctly. The clusterresolver will be able to...

P2
Type: Internal Cleanup
Area: xDS

With the switch to the new encoding API and the `mem` package, we have a TODO and some commented out code here: https://github.com/grpc/grpc-go/blob/master/rpc_util.go#L880-L900 It looks like there are no current...

Type: Bug
Area: RPC Features

Currently, when the xDS client encounters errors while decoding resources, the metadata indicates a NACKed update. However, the returned error lacks specific classification for these NACK errors. This makes it...

P2
Type: Bug
Area: xDS

The current end-to-end tests for xdsclient utilize a watcher implementation with a channel size of 1. This limitation prevents us from testing scenarios involving multiple updates with a combination of...

P2
Type: Internal Cleanup
Area: Testing

There is a race when a Subchannel goes from CONNECTING to READY to IDLE that prevents the READY state change notification. We should fix this, as this is causing specific...

P2
Type: Bug
Area: Client

In prior gRPC versions, the stats handler provided direct access to raw serialized data through payload.Data in `*stats.InPayload`. This functionality enabled certain applications to retrieve unmodified byte data directly. While...

Type: Question
Area: RPC Features