majusko / grpc-jwt-spring-boot-starter

Spring boot starter for gRPC framework with JWT authorization
Other
39 stars 7 forks source link

Bump grpc-testing from 1.41.0 to 1.49.2 #154

Closed dependabot[bot] closed 2 years ago

dependabot[bot] commented 2 years ago

Bumps grpc-testing from 1.41.0 to 1.49.2.

Release notes

Sourced from grpc-testing's releases.

v1.49.1

Bug Fixes

  • xds: Fix a bug in ring-hash load balancing policy that, during TRANSIENT_FAILURE state, it might cause unnecessary internal connection requests on subchannels. (#9537)
  • auth: Fix AppEngine failing while retrieving access token when instantiating a blocking stub using AppEngineCredentials (#9524)

Behavior Changes

v1.49.0

New Features

  • okhttp: Add OkHttpServerBuilder. The server can be used directly, but is not yet available via ServerBuilder.forPort() and Grpc.newServerBuilderForPort(). It passes our tests, but has seen no real-world use. It is also lacking connection management features
  • okhttp: Add support for byte-based private keys via TlsChannelCredentials and TlsServerCredentials
  • core: New outlier detection load balancer
  • googleapis: google-c2p resolver is now stabilized

Bug Fixes

  • core: Fix retry causing memory leak for canceled RPCs. (#9360)
  • core: Use SyncContext for InProcess transport callbacks to avoid deadlocks. This fixes the long-standing issue #3084 which prevented using directExecutor() in some tests using streaming RPCs
  • core: Disable retries with in-process transport by default (#9361). In-process does not compute message sizes so can retain excessive amounts of memory
  • bazel: Use valid target name for services and xds when overriding Maven targets (#9422). This fixes an error of the form no such target '@io_grpc_grpc_java//services:services' for services and missing ORCA classes for xds. The wrong target names were introduced in 1.47.0
  • xds: channel_id hash policy now uses a random per-channel id instead of an incrementing one. The incrementing id was the same for every process of a binary, which was not the intention (#9453)
  • core: Fix a bug that the server stream should not deliver halfClose() when the call is immediately canceled. The bug causes a bad message INTERNAL, desc: Half-closed without a request at server call. (#9362)
  • xds: Remove shaded orca proto dependency in ORCA api. The shading was broken and couldn't really be used. (#9366)

Behavior Changes

  • gcp-observability: Interceptors are now injected in more situations, including for non-Netty transports and when using transport-specific APIs like NettyChannelBuilder. (#9309 #9312 #9424)
  • gcp-observability: custom tags now extended to metrics and traces (#9402 #9407)
  • gcp-observability: excludes RPCs into Google Cloud Ops backend for instrumentation (#9436)
  • xds: xdsNameResolver now matches channel overrideAuthority in virtualHost matching (#9405)

Acknowledgement

@​benjaminp @​j-min5u

v1.48.1

New Features

ORCA provides APIs to inject custom metrics at a gRPC server, and consume them at a gRPC client. It implements A51: Custom Backend Metrics Support. We changed the ORCA APIs; they had broken shading and couldn't really be used, so we fixed them in the patch release.

Bug Fixes

  • core: Fix a bug that the server stream should not deliver halfClose() when the call is immediately canceled. The bug causes a bad message INTERNAL, desc: Half-closed without a request at server call. (#9362)
  • core: Fix retry causing memory leak for cancelled RPCs. (#9415)
  • core: Disable retry by default for in-process transport's channel.(#9368)

v1.48.0

Bug Fixes

  • Removed the Class-Path manifest entry from jars generated with the gradle shadow plugin (#9270). This should prevent “[WARNING] [path] bad path element” compilation warnings
  • Fix Channelz HTTP/2 window reporting. Previously the sender and receiver windows were reversed
  • Service config parse failures should be UNAVAILABLE, not INVALID_ARGUMENT (#9346). This bug could cause RPCs to fail with INVALID_ARGUMENT if the service config was invalid when the channel started. RPCs were not failed if the channel had previously received no config or a valid config. Channels using xds were not exposed to this issue

... (truncated)

Commits
  • 6eed4f8 Bump version to 1.49.2
  • adf9546 Update README etc to reference 1.49.2
  • 44281ac Bump Protobuf to 3.21.7
  • 069e670 Bump version to 1.49.2-SNAPSHOT
  • eb32ed1 Bump version to 1.49.1
  • c1e9c2b Update README etc to reference 1.49.1
  • 8b9acff core: outlier detection max ejection logic update (#9492) (#9552)
  • 0707aac core: outlier detection to min host request volume (#9490) (#9551)
  • 0e4e716 core: Update outlier detection max ejection logic. (#9489) (#9550)
  • e55bf31 xds: ringhash policy in TRANSIENT_FAILURE should not attempt connecting when ...
  • Additional commits viewable in compare view


Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
dependabot[bot] commented 2 years ago

Superseded by #155.