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:
v1.74.2
->v1.76.0
1.74.0
->1.76.0
1.74.0
->1.76.0
1.74.0
->1.76.0
1.74.0
->1.76.0
1.74.0
->1.76.0
Caution
This PR is marked as draft, as some updates cannot be made automatically (e.g. grpc-java protoc plugin)
Release Notes
grpc/grpc-go (google.golang.org/grpc)
v1.76.0
: Release 1.76.0Compare Source
Dependencies
Bug Fixes
INTERNAL
when a server sends zero response messages for a unary or client-streaming RPC. (#8523)INTERNAL
instead ofUNKNOWN
upon receiving http headers with status 1xx andEND_STREAM
flag set. (#8518)IDLE
state on backend address change. (#8615)New Features
credentials/jwt
package providing file-based JWT PerRPCCredentials (A97). (#8431)Performance Improvements
v1.75.1
: Release 1.75.1Compare Source
Bug Fixes
v1.75.0
: Release 1.75.0Compare Source
Behavior Changes
DelayedPickComplete
event, a type alias ofPickerUpdated
. (#8465)PickerUpdated
symbol.grpc.WithAuthority
as the highest-priority option for setting authority, above the setting in the credentials themselves. (#8488)WithAuthority
is available, the credentials should not be used to override the authority.New Features
GRPC_ENABLE_TXT_SERVICE_CONFIG
) to provide a way to disable TXT lookups in the DNS resolver (by setting it tofalse
). By default, TXT lookups are enabled, as they were previously. (#8377)Bug Fixes
call
andendpoint
in curly braces to comply with UCUM and gRPC OpenTelemetry guidelines. (#8481)grpc.NewClient(":<port-number-or-name>")
). (#8488)v1.74.3
: Release 1.74.3Compare Source
Bug Fixes
grpc/grpc-java (io.grpc:grpc-api)
v1.76.0
Compare Source
Bug Fixes
Improvements
New Features
Documentation
Dependencies
Thanks to
@JoeCqupt
@Sangamesh1997
@benjaminp
@camelcc
@dmytroreutov
@duckladydinh
@jirkafm
@kilink
@panchenko
@umairk79
@vimanikag
@werkt
@xuhongxu96
@zrlw
v1.75.0
Compare Source
Behavior Changes
Bug Fixes
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 nanosecond6ff8eca
). 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.c4256ad
). You should no longer see “Connection timeout for priority” errors.Improvements
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.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.9193701
). Client channel and server builders with interceptors and factories respectively for stats and tracing.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.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.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.Metadata
values to be exchanged during a call (#12229) (8021727
)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.XdsClientImpl
andControlPlaneClient
(#12287).ControlPlaneClient
uses "xds-cp-client" now instead of "xds-client" while logging.Dependencies Changes
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.jar_jar
to avoid xds deps (#12243) (8f09b96
). The //xds and //xds:orca targets now usejar_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 managementDocumentation
@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 deprecatedBinderChannelBuilder#bindAsUser
has always required SDK_INT >= 30. This change just copies that requirement forward to its replacement APIs inAndroidComponentAddress
and the TARGET_ANDROID_USERNameResolver.Args
.NameResolver.Listener2
interface (#12220) (d352540
)Thanks to
@benjaminp
@werkt
@kilink
@vimanikag
View the repository job log