grpc-go
grpc-go copied to clipboard
grpc
The Go language implementation of gRPC. HTTP/2 based RPC
### Use case(s) - what problem will this feature solve? Allow the use of the `match_string` in envoyproxy/go-control-plane XDS support for gRPC clients. Currently, only the deprecated API is supported....
RELEASE NOTES: - In accordance with issue #5454, I have added an example illustrating the use of `stats.Handler` in the `examples/features/stats_monitoring/` directory.
https://github.com/grpc/grpc-go/actions/runs/3085807967/jobs/4989513895
https://github.com/grpc/grpc-go/blob/60eecd9169ddc74ee6cf4bd52e2e06ef6766c5b7/internal/transport/http2_server.go#L235 I was looking at the write code - for net.Conn this works as expected, but if TLS is used conn will be tls.Conn so the line will not set...
https://github.com/grpc/proposal/blob/master/A47-xds-federation.md#lrs-server-representation talks about the changes required to support LRS with federation. We have changed the LB policy configs of `xds_cluster_resolver` and `xds_cluster_impl` to accept server config for the LRS server....
--go-grpc_out=require_unimplemented_servers should be --go-grpc_opt=require_unimplemented_servers https://github.com/grpc/grpc-go/blob/master/cmd/protoc-gen-go-grpc/README.md
Update `staticcheck` to the Go version listed in our go.mod. Also, update the list of checks ignored to remove ST1015 and add ST1019. There are no warnings firing currently from...
`fe80::1ff:fe23:4567:890a%eth2` is a valid IPv6 address, and should be supported in the DNS resolver ``` net.Dial("dns:///fe80::1ff:fe23:4567:890a%eth2:8080") ``` It fails with `ParseIP` error now. https://en.wikipedia.org/wiki/IPv6_address#Scoped_literal_IPv6_addresses
