Update grpc-java monorepo to v1.72.0 #112
Open
Conversation
This file contains hidden or 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}
renovate
bot
force-pushed
the
renovate/grpc-java-monorepo
branch
from
8d47c52 to
cb9dac3
Compare
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/grpc-java-monorepo
branch
from
cb9dac3 to
d60132f
Compare
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/grpc-java-monorepo
branch
from
d60132f to
524ac09
Compare
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/grpc-java-monorepo
branch
from
524ac09 to
c04564f
Compare
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/grpc-java-monorepo
branch
from
c04564f to
4528447
Compare
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/grpc-java-monorepo
branch
from
4528447 to
fd08624
Compare
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/grpc-java-monorepo
branch
from
fd08624 to
8614c85
Compare
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/grpc-java-monorepo
branch
from
8614c85 to
6aa92cb
Compare
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/grpc-java-monorepo
branch
from
6aa92cb to
9f42dae
Compare
renovate
bot
force-pushed
the
renovate/grpc-java-monorepo
branch
from
9f42dae to
74d34b2
Compare
renovate
bot
changed the title
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/grpc-java-monorepo
branch
from
74d34b2 to
9c8de32
Compare
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/grpc-java-monorepo
branch
from
9c8de32 to
ae08714
Compare
renovate
bot
changed the title
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/grpc-java-monorepo
branch
from
ae08714 to
6ac43f2
Compare
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/grpc-java-monorepo
branch
from
6ac43f2 to
9707da2
Compare
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/grpc-java-monorepo
branch
from
9707da2 to
6fa79f0
Compare
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/grpc-java-monorepo
branch
from
6fa79f0 to
7906c6b
Compare
renovate
bot
changed the title
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.47.0->1.72.01.47.0->1.72.01.47.0->1.72.0Warning
Some dependencies could not be looked up. Check the Dependency Dashboard for more information.
Release Notes
grpc/grpc-java (io.grpc:grpc-stub)
v1.72.0Compare Source
API Changes
f207be3). It is rarely used outside of gRPC itself. The configuration is passed as lb policy configuration instead1958e42)892144d)Bug Fixes
ca4819a)d82613a)94f8e93)8681786)Improvements
a57c14a)fca1d3c)e80c197). 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 transition3961a92). 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 details2e260a4). 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 IDLE7507a9e)350f90e)c340f4a)602aece)2f52a00). gRPC will no longer observe the HTTP/2 priorities, which were not used directly by gRPC and deprecated in RFC 9113666136b)a6e1c1f)New Features
1219706)cdab410)Thanks to
@panchenko
@emmanuel-ferdman
@JoeCqupt
v1.71.0Compare Source
API 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.0Compare Source
Bug 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.1Compare Source
Bug 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.0Compare Source
v1.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.1Compare Source
v1.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
v1.68.0: MISTAKEThis was supposed to be v1.67.0, but there was a mistake during the release process. This has everything in v1.67.1, except for:
v1.67.1gRPC Java 1.67.1 Release Notes
There was no 1.67.0 release. There was a problem making the release and it went to Maven Central as 1.68.0 instead. This is a version-corrected release.
Improvements
90d0fab)e821d5e). This makes it clearer whether a leak is a gRPC leak or an application leak when the Detachable API is being used6a9bc3b)72a977b)6dbd1b9)d034a56)96a788a)0017c98)c29763d)10d6002). Previously, RLS configuration would not have been updatedBug Fixes
cc1cbe9)c63e354)f866c80). This change applies to all petiole load balancing policies. For regular usages that use dns name resolution, this is unlikely to matter as the default dns name resolver returns consistent addresses. But this might improve LB behavior for some custom load balancers1dae144)448ec4f)Dependencies
70ae832)75012a5)ff8e413)Thanks to
@Juneezee
@lujiajing1126
@JarvisCraft
@sunpe
v1.66.0gRPC Java 1.66.0 Release Notes
API Changes
25a8b7c)AdvancedTlsX509TrustManager, anX509ExtendedTrustManagerthat allows users to configure advanced TLS features, such as root certificate reloading and peer cert custom verification. (658cbf6)GracefulSwitchLoadBalancerconfig (ebed047) and mark switchTo() deprecated. (85e0a01).GracefulSwitchLoadBalancernow receives its configuration like a regular load balancer.AllowSecurityPolicyto allow calling code to not have to wait on async/slow implementations.BinderTransportnow submits async implementations to an executor. (#11272) (7fee6a3)ServerBuilderfor adding a list of service implementations to the handler registry together. (#11285) (85ed053)Improvements
5ec0187)36e687f). There are now examples for both non-bzlmod and bzlmod.PickFirstLeafLoadBalancer062ebb4)NettyAdaptiveCumulatorif Netty is on version 4.1.111 or later. (#11367)21dec30)BinderServerownServerAuthInterceptor's executor that helps avoid leaks. (#11293) (15ad9f5)ProtoReflectionServiceV1for the v1 reflection protocol. The preexistingProtoReflectionServiceimplements the v1alpha reflection protocol. (#11237) (0aa976c)Bug Fixes
14fd81f)AdvancedTlsX509TrustManagervalidation on servers when using SSLSocket. Previously it would try to use a null SSLEngine . (dcb1c01)Dependencies
71eb5fb). This adds a runtime dependency on libstdc++a977385)a977385)a977385)a977385)a977385)a977385)a977385)a977385)a977385)e7c3803)@com_github_cncf_udpausage with preexisting@com_github_cncf_xds; delete@com_github_cncf_udparepo alias for xds (6dd6ca9)1611a73(c540993). The version used by Gradle had been updated in 1.62.0 (68334a0), but the bazel version had not7a25e68). Bazel’s protobuf rules no longer use the old com_google_protobuf_javalite repository named3c2f5a). Protobuf’s targets are generally just used directly; this fixed the only place that used maven’sartifact()syntaxThanks to
@hlx502
@erm-g
@jdcormie
@JoaoVitorStein
@cfredri4
v1.65.1Compare Source
What's Changed
v1.65.0Compare Source
grpc-netty in this release is compatible with Netty 4.1.111; it fixes the incompatibility that caused data corruption. grpc-netty-shaded is still using Netty 4.1.100.
New Features
df8cfe9)Improvements
ClientStreamTracer.inboundHeaders(Metadata)(960012d). This is the same as the existinginboundHeaders(), but is provided the Metadata6ec744f)8844cf7). This could be viewed as a small performance optimization, but mainly reduces the amount of race-handling code781b4c4) This change shows@ExperimentalApibeing removed, but it was re-added in3c97245before the releasec31dbf4)791f894)Bug fixes
fea577c). This was a long-standing race that could cause RPCs to hang, but was very unlikely to be hit. Avoiding the double-picking (8844cf7) made the race more visible0fea7dd). The previous behavior easily caused data corruptiona28357e). Previously, shutting down when a new connection was being established could result in the server never becoming terminatede4e7f3a). This issue was unlikely to be hit outside of specialized testsd57f271). This fixes a regression introduced in 1.62.234ee600)1670e97)f995c12)Thanks to
@hakusai22
@firov
@mateusazis
@Mir3605
@niloc132
v1.64.2What's Changed
v1.64.1What's Changed
v1.64.0Avoid upgrading your application to Netty 4.1.111, with this version as there is a possible corruption. For Netty 4.1.111 compatibility, it is best to use 1.63.2, 1.64.2, 1.65.1, and later. See https://github.com/grpc/grpc-java/issues/11284 .
API Changes
jakarta_omitwas renamed@generated=omit(#11086) (8a21afc)New Features
4561bb5)5ba1a55). The feature is still missing documentation and an example. It only supports metrics; tracing and logs will be future enhancements. See gRFC A66d1890c0)@maventargets (0064991)8050723)06df25b,35a171b,2897b39), to be exported by grpc-opentelemetry if explicitly enabled in GrpcOpenTelemetry. See gRFC A78a9fb272,a1d1932,8133318), to be exported by grpc-opentelemetry if explicitly enabled in GrpcOpenTelemetryImprovements
58de563)e036b1b). This will greatly improve the debuggability of certain server errors in particular cases. Instead of the client seeing “CANCELLED: RST_STREAM closed stream. HTTP/2 errConfiguration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR is behind base branch, 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.