This repository was archived by the owner on Feb 12, 2025. It is now read-only.
Open
Conversation
20809b5 to
4ed4998
Compare
4ed4998 to
148ef65
Compare
148ef65 to
eec2259
Compare
eec2259 to
90fc46a
Compare
90fc46a to
0853161
Compare
0853161 to
2c990b6
Compare
2c990b6 to
a52b395
Compare
a52b395 to
1762dab
Compare
1762dab to
e80de1b
Compare
e80de1b to
afc324b
Compare
afc324b to
a531893
Compare
a531893 to
6f81840
Compare
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
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.60.0->1.65.01.60.0->1.65.01.60.0->1.65.01.60.0->1.65.0Release Notes
grpc/grpc-java (io.grpc:grpc-stub)
v1.65.0grpc-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.1What's Changed
v1.64.0Avoid upgrading your application to Netty 4.1.111, as there is a possible corruption. Still investigating. 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 error code: CANCEL”, they could see “RESOURCE_EXHAUSTED: gRPC message exceeds maximum size4194304:6144592”f7ee5f3)e36f099)10cb4a3)537dbe8)load()statements for the Bazel builtin top-level java symbols (#11105) (add8c37)StatusProto.toStatusExceptionoverload to acceptThrowable(#11083) (5c9b492)Bug fixes
bdb6230)2c5f0c2). Previously the visible state change fromchannel.getState()was delayed until the name resolver returned results. This had no impact to RPC behaviore630593)6e97b18). These races had not been witnessed in practicef9b6e5f). This fixes a regression introduced by6e97b18that could hang RPCs instead of using fallback, but fixes a pre-existing bug that could greatly delay RPCs from using fallback.da619e2). This could have caused backoff entries to improperly be considered expired097a46b). The credential does its own verification and the default needs to be disabled for SPIFFEfb9a108)d21fe32)Dependencies
5a8da19)c703a1e)163efa3)77e59b2)Acknowledgements
@panchenko
@Ashok-Varma
@benjaminp
@AutomatedTester
@hypnoce
@keith
@laglangyue
@rostik404
@ryanpbrewster
@abtom
@hvadehra
@rtadepalli
v1.63.1Bug fixes
fb9a108)v1.63.0API Changes
0d749c5)ff34d51)257d1c2)2c83ef0)New Features
xds, dual stack, happy eyeballs: Support dual stack in xds, change list includes:
8a9ce99)38f968f)c61fe69)51f811d)Improvements
eba699a)ce2adcc)3abab95). When the deadline triggered and the deadline was set on the RPC via the stub or CallOptions, gRPC would gather additional debugging information to help understand where the RPC took so long. However if the deadline came from io.grpc.Context the error was simply “context timed out.” Now the debugging information is provided in both casese19f1f1)0d39c2c). Pass the optionjakarta_omitto protoc-gen-grpc-java when generating codefeab4e5).grpc-xdsjar size has decreased by 35%.867e469)a68399a)0b82f01)Bug Fixes
f4cc166). This fixes a possible regression introduced in 1.60.0. Auditing the buggy code showed it unlikely to cause problems in practice, but that was more by happenstance than by designd7628a3)aa90768). The remote race could cause an RPC to hang until its deadline. It had been seen in practice when the client was severely CPU under-provisioned78b3972)Dependencies
Acknowledgement
Alex Panchenko
Benjamin Peterson
David Ankin
Prashanth Swaminathan
Touko Vainio-Kaila
v1.62.2gRPC Java 1.62.2 Release Notes
Note that this is the initial 1.62.x release
API Changes
io.grpc.services.BinaryLogs, which was deprecated since 2021.io.grpc.protobuf.services.BinaryLogsshould be used instead (#10832).6d96e65)New Features
Improvements
cb03bd2). This is mostly a behind-the-scenes change to adjust to the newer way Bazel operates65a6b3b). Neither binary uses runfiles, but the task will be ready if they need to in the future100d5a5)7ba0718)Bug Fixes
Dependencies
Acknowledgements
v1.61.1Bug Fixes
xds: Fix a bug in
WeightedRoundRobinLoadBalancerpolicy that could raiseNullPointerExceptionand further cause channel panic when picking a subchannel. This bug can only be triggered when connection can not be established and the channel reportsTRANSIENT_FAILUREstate. (#10868)v1.61.0API Changes
860b5cb)New Features
Improvements
201893f)round_robinpickers (dca89b2). This makes its implementation more similar toweighted_round_robin.Bug Fixes
8ac43dd). The Gradle test fixtures are for use by grpc-java's internal tests.Dependencies
55a9c01). Bazel 7 is available, and Protobuf has already dropped support for Bazel 5.d6830d7). This reduces the transitive classes "leaked" into the compile classpath. In particular, grpc-core (io.grpc.internal) will be less frequently included transitively at compile time.c985797)Acknowledgements
v1.60.2Bug Fixes
xds: Fix a bug in
WeightedRoundRobinLoadBalancerpolicy that could raiseNullPointerExceptionand further cause channel panic when picking a subchannel. This bug can only be triggered when connection can not be established and the channel reportsTRANSIENT_FAILUREstate. (#10868)v1.60.1Bug Fixes
Configuration
📅 Schedule: Branch creation - "every weekend" (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.