aws-otel-java-instrumentation
aws-otel-java-instrumentation copied to clipboard
Bump io.grpc:grpc-stub from 1.56.1 to 1.72.0
trafficstars
Bumps io.grpc:grpc-stub from 1.56.1 to 1.72.0.
Release notes
Sourced from io.grpc:grpc-stub's releases.
V1.72.0
API Changes
- util: Remove deprecated method GracefulSwitchLb.switchTo() (f207be39a). It is rarely used outside of gRPC itself. The configuration is passed as lb policy configuration instead
- xds: Add support for custom per-target credentials on the transport (#11951) (1958e4237)
- xds: Explicitly set request hash key for the ring hash LB policy (892144dca)
Bug Fixes
- core: Apply ManagedChannelImpl's updateBalancingState() immediately (ca4819ac6)
- xds: Fix cluster selection races when updating config selector (d82613a74)
- otel: Fix span names as per the A72 gRFC changes (#11974) (94f8e9369)
- xds: ClusterResolverLoadBalancer handle update for both resolved addresses and errors via ResolutionResult (#11997) (868178651)
Improvements
- netty: Avoid allocating an exception on transport shutdown. This reduces allocation rate for connection-heavy workloads/load testing (a57c14a51)
- servlet: Set an explicit description for CANCELLED status (#11927) (fca1d3cf4)
- xds: gRFC A74 xDS Config Tears implementation in the XdsNameResolver (e80c19745). While there is more remaining, users may already see reduced latency when resources are replaced. For example, if changing a route from one backend service to another, RPCs may see less latency during the transition
- core: Log any exception during channel panic because of exception (3961a923a). This prevents the exception from propagating up the stack on an arbitrary thread. Such exceptions are rarely interesting. Instead, the exception that caused the channel panic is the important one, and RPCs will still fail with its details
- util: Graceful switch to new LB when leaving CONNECTING (2e260a4bb). Previously when using xDS and the configuration changes the LB policy, the old LB policy is used until the new one is READY. Now the old LB policy is used until the new policy becomes READY, TRANSIENT_FAILURE, or IDLE
- core: Use java.time.Time.getNano directly in InstantTimeProvider. Previously reflection was used which would confuse R8 full mode (#11977) (7507a9ec0)
- core: Avoid cancellation exceptions when notifying watchers that already have their connections cancelled (#11934) (350f90e1a)
- rls: allow maxAge in RLS config to exceed 5 minutes if staleAge is set. Previously, the limit was 5 minutes, which isn't enough for some gRPC clients (#11931) (c340f4a2f)
- xds: avoid unnecessary dns lookup for CIDR addresses (#11932) (602aece08)
- netty: Swap to UniformStreamByteDistributor (#11954) (2f52a0036). gRPC will no longer observe the HTTP/2 priorities, which were not used directly by gRPC and deprecated in RFC 9113
- core: Avoid Set.removeAll() when passing a possibly-large List (#11994) (666136b4b)
- stub: trailersFromThrowable() metadata should be copied (#11979) (a6e1c1f09)
New Features
- xds: xDS-based HTTP CONNECT configuration (#11861) (12197065f)
- netty: Per-rpc authority verification against peer cert subject names. Overriding transport authority at rpc time is only allowed when using TlsChannelCredentials. The per-rpc authority verification feature is guarded by the environment variable GRPC_ENABLE_PER_RPC_AUTHORITY_CHECK in this release. When this is false or not set, the rpc will not fail when the authority verification fails but a warning will be logged. In a subsequent release the usage of this environment variable will be removed and RPCs will start failing if the authority doesn't match the peer certificate names. The environment variable is temporary; if you are depending on the existing insecure behavior, please file an issue (#11724) (cdab410b8)
Thanks to
@panchenko@emmanuel-ferdman@JoeCquptV1.71.0
API Changes
- xds: Enable Xds Client Fallback by default. This allows having a backup xDS server as described in gRFC A71-xds-fallback.md (#11817) (176f3eed1)
- protobuf: Experimental API marshallerWithRecursionLimit in
ProtoUtilsis now stabilized (#11884) (90b1c4fe9)Bug Fixes
- xds: Cluster weights should be uint32 (199a7ea3e). They were previously processed as int32, although the sum of weights was checked to be positive. So this would have caused a very large weight to never be selected and to reduce the chances of immediately-following clusters to be selected. There have been no reports of control planes using such large weights
- xds: Fix an unlikely infinite loop triggered by route update (199a7ea3e). Triggering required the old cluster to no longer be used, an RPC processing when the update arrived, and for a RPC to not match any route in the new config. There have been no reports of this actually happening
- core: Release data frame if it is received before the headers (dc316f7fd)
... (truncated)
Commits
b0794e4Bump version to 1.72.0a2b642cUpdate README etc to reference 1.72.0b4e635dstub: Utility method StreamObservers.nextAndComplete() that does both onNext ...a6e1c1fstub: trailersFromThrowable() metadata should be copied (#11979) (#12008)8681786xds: ClusterResolverLoadBalancer handle update for both resolved addresses an...666136bcore: Avoid Set.removeAll() when passing a possibly-large List (#11994) (#12000)2448c8butil: Replace BUFFER_PICKER with FixedResultPicker2e260a4util: Graceful switch to new LB when leaving CONNECTING7507a9ecore: Use java.time.Time.getNano in InstantTimeProvider without reflection (#...a332eddfix: cleans up FileWatcherCertificateProvider in XdsSecurityClientServerTest- Additional commits viewable in compare view
You can trigger a rebase of this PR by commenting @dependabot rebase.
Dependabot will merge this PR once CI passes on it, as requested by @thpierce.
Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
Note Automatic rebases have been disabled on this pull request as it has been open for over 30 days.