Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
49114: vendor: bump grpc to v1.27.1 r=petermattis a=tbg Upgrade gRPC to 1.27.1 (latest is 1.29). This doesn't pick up anything that we need, but it claims to contain some improvements, and now is the right time in the cycle to bump if we're going to. TODO: does this want a release note? Notable PRs (from gRPC-go's release notes): - client: fix race between client-side stream cancellation and compressed server data arriving (grpc/grpc-go#3054) - clientconn: fix potential deadlock caused by ResetConnectBackoff (grpc/grpc-go#3051) - internal: fix context leak when stream is not created successfully (grpc/grpc-go#2985) - server: set and advertise max frame size of 16KB (grpc/grpc-go#3018) - transport: block reading frames when too many transport control frames are queued (grpc/grpc-go#2970) Addresses CVE-2019-9512 (Ping Flood), CVE-2019-9514 (Reset Flood), and CVE-2019-9515 (Settings Flood). - server: avoid an unnecessary allocation per-RPC for OK status (grpc/grpc-go#2920) Special Thanks: @dzbarsky - server: avoid call to trace.FromContext and resulting allocations when tracing is disabled (grpc/grpc-go#2926) Special Thanks: @dzbarsky - http2client: remove unnecessary allocations for header fields (grpc/grpc-go#2925) Special Thanks: @dzbarsky - status: avoid allocations when returning an OK status (grpc/grpc-go#2929) Special Thanks: @dzbarsky - server: avoid allocations related to tracking excessive pings (grpc/grpc-go#2923) Special Thanks: @dzbarsky - transport: call Unlock in defer to avoid data race (grpc/grpc-go#2953) - client: fix canceled vs deadline exceeded double-check logic (grpc/grpc-go#2906) - client: fix race between transport draining and new RPCs (grpc/grpc-go#2919) Release note (general change): gRPC was updated from 1.21 to 1.27.1. Co-authored-by: Tobias Schottdorf <[email protected]>
- Loading branch information