fix(deps): Update grpc-java monorepo to v1.75.0

[cq-bot]

This PR contains the following updates:

Package	Type	Update	Change
io.grpc:protoc-gen-grpc-java	dependencies	minor	1.73.0 -> 1.75.0
io.grpc:grpc-testing	dependencies	minor	1.73.0 -> 1.75.0
io.grpc:grpc-netty-shaded	dependencies	minor	1.73.0 -> 1.75.0
io.grpc:grpc-stub	dependencies	minor	1.73.0 -> 1.75.0
io.grpc:grpc-services	dependencies	minor	1.73.0 -> 1.75.0
io.grpc:grpc-protobuf	dependencies	minor	1.73.0 -> 1.75.0

---

Release Notes

grpc/grpc-java (io.grpc:protoc-gen-grpc-java)

v1.75.0

Behavior Changes

• binder: Introduce server pre-authorization (#​12127). grpc-binder clients authorize servers by checking the UID of the sender of the SETUP_TRANSPORT Binder transaction against some SecurityPolicy. But merely binding to an unauthorized server to learn its UID can enable "keep-alive" and "background activity launch" abuse, even if security policy ultimately causes the grpc connection to fail. Pre-authorization mitigates this kind of abuse by resolving addresses and authorizing a candidate server Application's UID before binding to it. Pre-auth is especially important when the server's address is not fixed in advance but discovered by PackageManager lookup.

Bug Fixes

• core: grpc-timeout should always be positive (#​12201) (6dfa03c). There is a local race between when the deadline is checked before sending the RPC and when the timeout is calculated to put on-the-wire. The code replaced negative timeouts with 0 nanoseconds. gRPC’s PROTOCOL-HTTP2 spec states that timeouts should be positive, so now non-positive values are replaced with 1 nanosecond

• core: Improved DEADLINE_EXCEEDED message for delayed calls (6ff8eca). Delayed calls are the first calls on a Channel before name resolution has resolved addresses. Previously you could see confusing errors saying the deadline “will be exceeded in” X time. The message tense was simply wrong, and now will be correct: deadline “was exceeded after” X time.

• xds: PriorityLB now only uses the failOverTimer to start additional priorities, not fail RPCs (c4256ad). You should no longer see “Connection timeout for priority” errors.

Improvements

• netty: Count sent RST_STREAMs against NettyServerBuilder.maxRstFramesPerWindow() limit (#​12288). This extends the Rapid Reset tool to also cover MadeYouReset. the reset stream count will cause a 420 "Enhance your calm response" to be sent. This depends on Netty 4.1.124 for a bug fix to actually call the encoder by the frame writer.

• xds: Convert CdsLb to XdsDepManager (297ab05). This is part of gRFC A74 to have atomic xDS config updates. This is an internal change, but does change the error description seen in certain cases, especially DEADLINE_EXCEEDED on a brand-new channel.

• census: APIs for stats and tracing (#​12050) (9193701). Client channel and server builders with interceptors and factories respectively for stats and tracing.

• stub: simplify BlockingClientCall infinite blocking (#​12217) (ba0a732). Move deadline computation into overloads with finite timeouts. Blocking calls without timeouts now do not have to read the clock.

• xds: Do RLS fallback policy eagar start (#​12211) (42e1829). In gRPC-Java, the xDS clusters were lazily subscribed, which meant the fallback target which is returned in the RLS config wasn’t subscribed until a RPC actually falls back to it. The delayed resource subscription process in gRPC Java made it more susceptible to the effects of the INITIAL_RESOURCE_FETCH_TIMEOUT compared to other programming languages. It also had impact beyond the RLS cache expiration case, for example, when the first time the client initialized the channel, we couldn't fallback when the intended target times out, because of the lazy subscription. This change starts the fallback LB policy for the default target at the start of RLS policy instead of only when falling back to the default target, which fixes the above mentioned problems.

• xds: Aggregate cluster fixes (A75) (#​12186) (7e982e4). The earlier implementation of aggregate clusters concatenated the priorities from the underlying clusters into a single list, so that it could use a single LB policy defined at the aggregate cluster layer to choose a priority from that combined list. However, it turns out that aggregate clusters don't actually define the LB policy in the aggregate cluster; instead, the aggregate cluster uses a special cluster-provided LB policy that first chooses the underlying cluster and then delegates to the LB policy of the underlying cluster. This change implements that.

• api: set size correctly for sets and maps in handling Metadata values to be exchanged during a call (#​12229) (8021727)

• xds: xdsClient cache transient error for new watchers (#​12291). When a resource update is NACKed, cache the error and update new watchers that get added with that error instead of making them hang.

• xds: Avoid PriorityLb re-enabling timer on duplicate CONNECTING (#​12289). If a LB policy gives extraneous updates with state CONNECTING, then it was possible to re-create failOverTimer which would then wait the 10 seconds for the child to finish CONNECTING. We only want to give the child one opportunity after transitioning out of READY/IDLE.

• xds: Use a different log name for XdsClientImpl and ControlPlaneClient (#​12287). ControlPlaneClient uses "xds-cp-client" now instead of "xds-client" while logging.

Dependencies Changes

• Upgrade to Netty 4.1.124.Final (#​12286). This implicitly disables NettyAdaptiveCumulator (#​11284), which can have a performance impact. We delayed upgrading Netty to give time to rework the optimization, but we've gone too long already without upgrading which causes problems for vulnerability tracking.

• bazel: Use jar_jar to avoid xds deps (#​12243) (8f09b96). The //xds and //xds:orca targets now use jar_jar to shade the protobuf generated code. This allows them to use their own private copy of the protos and drop direct Bazel dependencies on cel-spec, grpc, rules_go, com_github_cncf_xds, envoy_api, com_envoyproxy_protoc_gen_validate, and opencensus_proto. This mirrors the shading of protobuf messages done for grpc-xds provided on Maven Central and should simplify dependency management

Documentation

• Clarify requirements for creating a cross-user Channel. (#​12181). The @SystemApi runtime visibility requirement isn't really new. It has always been implicit in the required INTERACT_ACROSS_USERS permission, which can only be held by system apps in production. Now deprecated BinderChannelBuilder#bindAsUser has always required SDK_INT >= 30. This change just copies that requirement forward to its replacement APIs in AndroidComponentAddress and the TARGET_ANDROID_USER NameResolver.Args.

• api: Add more Javadoc for NameResolver.Listener2 interface (#​12220) (d352540)

Thanks to

@​benjaminp
@​werkt
@​kilink
@​vimanikag

v1.74.0

Behavior Changes

• compiler: Default to @generated=omit (f8700a1). This omits javax.annotation.Generated from the generated code and makes the org.apache.tomcat:annotations-api compile-only dependency unnecessary (README and examples changes forthcoming; we delayed those changes until the release landed). You can use the option @generated=javax for the previous behavior, but please also file an issue so we can develop alternatives
• compiler: generate blocking v2 unary calls that throw StatusException (#​12126) (a16d655). Previously, the new blocking stub API was identical to the older blocking stub for unary RPCs and used the unchecked StatusRuntimeException. However, feedback demonstrated it was confusing to mix that with the checked StatusException in BlockingClientCall. Now the new blocking stub uses StatusException throughout. grpc-java continues to support the old generated code, but the version of protoc-gen-grpc-java will dictate which API you see. If you support multiple generated code versions, you can use the older blocking v1 stub for unary RPCs

Bug Fixes

• netty: Fix a race that caused RPCs to hang on start when a GOAWAY was received while the RPCs’ headers were being written to the OS (b04c673, 15c7573). This was a very old race, not a recent regression. All streams should now properly fail instead of hanging, although in some cases they may be transparently retried
• util: OutlierDetection should use nanoTime, not currentTimeMillis (#​12110) (1c43098). Previously, changes in the wall time would impact its accounting
• xds: Don't allow hostnames in address field in EDS (#​12123) (482dc5c). Only IP addresses were handled properly, and only IP addresses should be handled per gRFC A27
• xds: In resource handling, call onError() for RDS and EDS NACKs (#​12122) (efe9ccc). Previously the resource was NACKed, but gRPC would continue waiting for the resource until a timeout was reached and claim the control plane didn’t send the resource. Now it will fail quickly with an informative error
• xds: Implement equals in RingHashConfig (a5eaa66). Previously all configuration refreshes were considered a new config, which had the potential for causing unexpected inefficiency problems. This was noticed by new code for gRFC A74 xDS Config Tears that is not yet enabled, so there are no known problems that this caused
• LBs should avoid calling LBs after lb.shutdown() (1df2a33). This fixed pick_first and ring_hash behavior that could cause rare and “random” races in parent load balancers like a NullPointerException in ClusterImplLoadBalancer.createSubchannel(), which had a ring_hash child. This is most likely to help xDS, as it heavily uses hierarchical LB policies

Improvements

• util: Deliver addresses in a random order to shuffle connection creation ordering (f07eb47). Previously, connections were created in-order (but non-blocking), so in a fast network the first address could be more likely to connect first given a "microsecond" headstart. That first connection then receives all the buffered RPCs, which could cause temporary, but repeated, load imbalances of the same backend when all clients receive the same list of addresses in the same order. This has been seen in practice, but it is unclear how often it happens. Shuffling has the potential to improve load distribution of new clients when using round_robin, weighted_round_robin, and least_request, which connect simultaneously to multiple addresses
• core: Use lazy message formatting in checkState (#​12144) (26bd0ee). This avoids the potential of unnecessarily formatting an exception as a string when a subchannel fails to connect
• bazel: Migrate java_grpc_library to use DefaultInfo (#​12148) (6f69363). This adds compatibility for --incompatible_disable_target_default_provider_fields
• binder: Rationalize @​ThreadSafe-ty inside BinderTransport (#​12130) (c206428)
• binder: Cancel checkAuthorization() request if still pending upon termination (#​12167) (30d40a6)

Dependencies

• compiler: Upgrade Protobuf C++ to 22.5 (#​11961) (46485c8). This is used by the pre-built protoc-gen-grpc-java plugin on Maven Central. This should have no visible benefit, but gets us closer to upgrading to Protobuf 27 which added edition 2023 support
• release: Migrate artifacts publishing changed from legacy OSSRH to Central Portal (#​12156) (f99b2aa). We aren’t aware of any visible changes to the results on Maven Central

---

Configuration

📅 Schedule: Branch creation - Between 12:00 AM and 03:59 AM, on day 1 of the month ( * 0-3 1 * * ) (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about these updates again.

---

• If you want to rebase/retry this PR, check this box

---

This PR has been generated by Renovate Bot.