Update grpc to v1.71.0 #7
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
![renovate[bot]](https://avatars.githubusercontent.com/in/2740?s=60&v=4){kind=small}
Remove useless code and remove code that makes errors.
Remove useless code, fix tickle feature and use better usage of component system.
This loads some important information's from the world.
…adow-8.x Update plugin com.gradleup.shadow to v8.3.6
Update dependency com.github.ben-manes.caffeine:caffeine to v3.2.0
Update dependency gradle to v8.13
…-bom-5.x Update dependency org.junit:junit-bom to v5.12.1
Renovate Ignore NotificationBecause you closed this PR without merging, Renovate will ignore this update ( If you accidentally closed this PR, or if you changed your mind: rename this PR to get a fresh replacement PR. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
1.68.0->1.71.01.68.0->1.71.01.68.0->1.71.01.68.0->1.71.0Warning
Some dependencies could not be looked up. Check the warning logs for more information.
Release Notes
grpc/grpc-java (io.grpc:grpc-okhttp)
v1.71.0API Changes
176f3ee)ProtoUtilsis now stabilized (#11884) (90b1c4f)Bug Fixes
199a7ea). 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 weights199a7ea). 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 happeningdc316f7)Improvements
CheckReturnValuewith Error Prone's (#11811) (7b5d069)5a7f350)44e92e2)7585b16). This makes it much easier to debug connectivity issues when using wait-for-ready RPCs0f5503e)MessageFramer.flush() is being called between every message, so messages are never combined and the larger allocation just wastes memory. (4a10a38,7153ff8)ClientStreamObservercloses the response observer log the error message if this operation fails (#11880) (302342c)3142928)c506190,b3db8c2). This was an internal refactor that should have no user-visible changeAltsContextUtilto allow getting theAltsContexton client-side (b1bc0a9)b44ebce)Documentation
HelloWorldServerto use Executor (#11850) (16edf7a)9e86299)Dependencies
fc8571a)122b683)Thanks to
@benjamin
@panchenko
@harshagoo94
@NaveenPrasannaV
v1.70.0Bug Fixes
8ea3629). Violations would only have triggered on API level 23 and earlier, and the violations fixed here were highly unlikely to be triggeredebe2b48). This fixes a regression introduced in 1.64.0. The regression should have caused failures on API level 23 and earlier when a StatusRuntimeException or StatusException was created. However, for unknown reasons tests on old devices didn’t notice issuesa0982ca). Hostnames are considered trusted and CAs are required to use punycode for non-ASCII hostnames, so this is expected to provide defense-in-depth. See also the related GoSecure blog post and the AOSP fix65b32e6)1cf1927). This (along with6c12c2b) fixes a nonce-handling regression introduced in 1.66.0 that could cause resources to appear to not exist until re-creating the ADS stream. Triggering the behavior required specific config changes. It is easiest to trigger when clusters use EDS and routes are changed from one cluster to another. The error “found 0 leaf (logical DNS or EDS) clusters for root cluster” might then be seen6c12c2b)e8ff6da). They were previously required to be strings6516c73). This fixes the error “Incorrect number of required labels provided. Expected: 4” introduced in 1.69.0f8f6139). This fixes clients treating large max_requests as “no requests” and failing all requestsImprovements
0b2d440)ea8c31c)805cad3)1126a8e)ef7c2d5)1edc4d8). Not used actively, but this adds validation. The validation is unlikely to fail but may reject invalid resources.ebb43a6). This only impacts thegrpc.targetlabel ingrpc.xds_client.*metrics. Previously the empty string was used7f9c1f3). This only matters when debug logging is enabledDocumentation
f1109e4)c96e926)5e8abc6)Dependencies
8a5f777)Thanks to
v1.69.1Bug Fixes
a0982ca). Hostnames are considered trusted and CAs are required to use punycode for non-ASCII hostnames, so this is expected to provide defense-in-depth. See also the related GoSecure blog post and the AOSP fix1cf1927). This (along with6c12c2b) fixes a nonce-handling regression introduced in 1.66.0 that could cause resources to appear to not exist until re-creating the ADS stream. Triggering the behavior required specific config changes. It is easiest to trigger when clusters use EDS and routes are changed from one cluster to another. The error “found 0 leaf (logical DNS or EDS) clusters for root cluster” might then be seen6c12c2b)e8ff6da). They were previously required to be stringsf8f6139). This fixes clients treating large max_requests as “no requests” and failing all requests6516c73). This fixes the error “Incorrect number of required labels provided. Expected: 4” introduced in 1.69.0v1.69.0v1.69.0
New Features
LoadBalancers to specify an authority per-RPC.(#11631) (c167ead) CallOptions.withAuthority() has higher precedence.735b3f3) The soft limit is a lower size limit that fails an increasing percentage of RPCs as the Metadata size approaches the upper limit. This can be used as an “early warning” that the Metadata size is growing too largeGoogleDefaultChannelCredentials(#11634) (ba8ab79)20d09ce).grpc.xds.authorityis not yet availableBug Fixes
ListeneronAddresses toListener2continue to use onResult (#11666) (dae078c). This fixes a 1.68.1 "IllegalStateException: Not called from the SynchronizationContext" regression (#11662) that could be seen in certain custom NameResolversef1fe87). This fixes a 1.68.1 NullPointerException regression when a custom transportExecutor was provided to the channel and it did not have enough threads to run new tasksImprovements
java.time.Durationoverloads toCallOptions,AbstractStubmethods that take TimeUnit and a time value (#11562) (766b923)9176b55). This increases the timestamp precision from millisecondsAndroidComponentAddressspecify a target UserHandle (#11670) (e58c998)a5db67d)29dd9ba). The target s2a had been referenced by IO_GRPC_GRPC_JAVA_OVERRIDE_TARGETS but didn’t previously existb170334). This compatibility is on the source level. There is not a pre-built binary on Maven Central that supports proto lite921f88a). The class implements the deprecated v1alpha of the reflection protocol. Prefer ProtoReflectionServiceV1, which implements the v1 version of the reflection protocolDependencies
1993e68)1993e68)1993e68)1993e68)1993e68)664f1fc). This had been done for the Maven Central binaries in 1.63.0, but had been missed for Bazel buildsDocumentation
fe350cf)a79982c)Thanks to
@niloc132
@rockspore
@SreeramdasLavanya
@vinodhabib
v1.68.3Bug Fixes
a0982ca). Hostnames are considered trusted and CAs are required to use punycode for non-ASCII hostnames, so this is expected to provide defense-in-depth. See also the related GoSecure blog post and the AOSP fix1cf1927). This (along with6c12c2b) fixes a nonce-handling regression introduced in 1.66.0 that could cause resources to appear to not exist until re-creating the ADS stream. Triggering the behavior required specific config changes. It is easiest to trigger when clusters use EDS and routes are changed from one cluster to another. The error “found 0 leaf (logical DNS or EDS) clusters for root cluster” might then be seen6c12c2b)e8ff6da). They were previously required to be stringsf8f6139). This fixes clients treating large max_requests as “no requests” and failing all requestsv1.68.2Bug Fixes
Improvements
v1.68.1v1.68.0 was a mistake. This is the first release of version 1.68.x
Bug Fixes
Behavior Changes
4be69e3). This is the existing behavior in C core. Duplicate keys in objects are dangerous as which value takes effect is undefined. Previously, the last value was used3a6be9c). The transport uses two threads, but one is on-demand. If the executor provided tobuilder.transportExecutor()runs out of threads (e.g., it is a fixed-size thread pool), all transports can be wedged, unable to run on-demand tasks, until keepalive kills one of them. Two threads are now used when handshaking a new transport, and the transport will time out after 1 second with “Timed out waiting for second handshake thread” if two threads are unavailablemesh_idvalue fromCSM_MESH_IDenvironment variable, instead of getting it from bootstrap file (84d30af)Improvements
782a44a) (#11599) (e59ae5f). This is aio.grpc.Contextstorage override to store its state inio.opentelemetry.context.Context. Libraries should not add a dependency on this artifact, as applications can only have one storage override in their classpathio.grpc.s2a.S2AChannelCredentials1ded8af)b692b9d). This expands the class of bugs that will fail RPCs with the panic error, versus some undefined behaviorfa26a8b)StreamTracer.inboundMessageRead()now reports uncompressed message size when the message does not need compression (#11598) (2aae68e). Previously it always reported-1(unknown)62f4098)6f35422). This is especially helpful when using TLS but not running on AndroidUdsChannelBuilder, use fake IP instead of localhost (a908b5e). This avoids an unnecessary DNS lookupf3cf7c3)99be6e9)46c1b38)94a0a0d)GRPC_EXPERIMENTAL_ENABLE_OTEL_TRACINGenvironment variable totrueto enable tracing support inGrpcOpenTelemetry(#11409, #11477)(043ba55,421e237)Dependencies
2ff837a)Thanks to:
@Juneezee
@lgalfaso
@bestbeforetoday
@hlx502
@JoeCqupt
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), 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.
This PR was generated by Mend Renovate. View the repository job log.