chore(deps): update grpc packages to v1.32.1 - #7300

v1.32.1

Compare Source

API Changes

• api: Removed deprecated method ChannelBuilder.blockingExecutor() (#​7242). There should not be any users as it was deprecated the first release it was available and was renamed offloadExecutor().
• grpclb: Make ATTR_LB_ADDRS public (#​7230). This is necessary to configure grpclb from a custom NameResolver

New Features

• xds: perform header matching on concatenated multi-valued headers (#​7215)
• xds: add header matching special cases for hiding/exposing some gRPC headers (#​7224). The only gRPC header available for header matching is “content-type”.
• xds: support load reporting all clusters option and fix actual report interval measurement (#​7209). If the LRS response enables send_all_clusters, the client side will report loads for all clusters it is currently using.

Bug Fixes

• core, alts, cronet: Fix ByteBuffer covariant method usages (#​7349). When built with Java 9+, internal usages of ByteBuffer APIs may cause runtime breakage for dependent applications running with Java 8. This is fixed now.
• core: Fixed a bug that RPC may hang when hedging is enabled with a throttling configuration (#​7337)
• netty: The environment variable GRPC_EXPERIMENTAL_AUTOFLOWCONTROL=false will now disable the BDP monitoring introduced in v1.30.0. This is intended to help diagnose a “too_many_pings” compatibility issue and will be removed once it is resolved. If you need to use the variable, please file an issue
• benchmarks: Use correct classpath for scripts (the ones in the bin/ folder of the tar/zip), fixing NoClassDefFoundErrors. The classpath was probably broken starting in v1.30.
• xds: routing policy should immediately update a picker that selects base on updated config (#​7233)

Dependencies

• netty: Upgrade to Netty 4.1.51 and tcnative 2.0.31
• android, cronet: Drop support for android SDK versions older than 16 (#​7253). The minimum supported Android SDK version is 16.

Acknowledgements

@​susinmotion
@​trustin
@​wanyingd1996

v1.31.1

Compare Source

Bug Fixes

• netty: The environment variable GRPC_EXPERIMENTAL_AUTOFLOWCONTROL=false will now disable the BDP monitoring introduced in v1.30.0. This is intended to help diagnose a “too_many_pings” compatibility issue and will be removed once it is resolved. If you need to use the variable, _please_ file an issue
• examples: some gRPC artifacts are missing in JCenter causing Android examples to sometimes fail to build. Now we are adding mavenCentral as fallback for the Android examples. See #​5782
• xds: meshCA protocol buffers added in v1.31.0 are now properly shaded in an internal package
• xds: fixed some internal breakage for traffic splitting

v1.31.0

Compare Source

API Changes

• api: ManagedChannelBuilder.nameResolverFactory is now marked deprecated. It has long been our plan to remove the function, but was not communicated. Most usages should be able to globally register via the SPI mechanism or NameResolverRegistry.register(). There is a plan to add a method to ManagedChannelBuilder to specify the default target scheme for the channel. If your use-case is not covered, please inform us on #​7133

New Features

• The following new xDS functionality is added in this release:
  • Requests matching based on path (prefix, full path and safe regex) and headers.
  • Requests routing to multiple clusters based on weights.
  • The xDS features supported in a given release are documented here.
• api: Added LoadBalancer.Helper.createResolvingOobChannelBuilder(). It is similar to LoadBalancer.Helper.createResolvingOobChannel() except allows configuring the channel (#​7136)

Bug Fixes

• netty: return status code unavailable when netty channel has unresolved InetSocketAddress (#​7023)
• core: fix a bug that a call may hang when using manual flow control and gRPC retry is enabled (#​6817)

Documentation

• stub: Documented more behavior of ClientCalls and ServerCalls, with regard to ClientResponseObserver, ClientCallStreamObserver, ServerCallStreamObserver, and exceptions
• api: Documented how Providers may be used in their respective class documentation. Previously you “just had to know” the SPI mechanism was available

Dependencies

• Update guava to 29.0 (#​7079)

Examples

• examples: Add client/server retrying example via service config #​7111

Acknowledgements

@​alexanderscott
@​AnarSultanov
@​cindyxue
@​d-reidenbach
@​elharo
@​gsharma
@​reggiemcdonald