dependabot[bot] opened a new pull request, #21237:
URL: https://github.com/apache/camel/pull/21237

   Bumps `grpc-version` from 1.78.0 to 1.79.0.
   Updates `io.grpc:grpc-all` from 1.78.0 to 1.79.0
   <details>
   <summary>Release notes</summary>
   <p><em>Sourced from <a 
href="https://github.com/grpc/grpc-java/releases";>io.grpc:grpc-all's 
releases</a>.</em></p>
   <blockquote>
   <h2>v1.79.0</h2>
   <p><strong>API Changes</strong></p>
   <ul>
   <li>
   <p>core: Delete the never-used 
io.grpc.internal.ReadableBuffer.readBytes(ByteBuffer) (<a 
href="https://redirect.github.com/grpc/grpc-java/issues/12580";>#12580</a>) 
(738782fb0). This is deeply internal and not accessible, so shouldn’t impact 
anything. However, Apache Arrow Java <a 
href="https://github.com/apache/arrow-java/blob/96156ccc2bf933c75c852ca7c04418a61f87defd/flight/flight-core/src/main/java/org/apache/arrow/flight/grpc/GetReadableBuffer.java#L44-L45";>uses
 reflection to access private fields</a>; <a 
href="https://redirect.github.com/apache/arrow-java/pull/954";>GH-939: Remove 
reflection for gRPC buffers</a> is swapping to gRPC’s public zero-copy APIs</p>
   </li>
   <li>
   <p>opentelemetry: Add target attribute filter for metrics (<a 
href="https://redirect.github.com/grpc/grpc-java/issues/12587";>#12587</a>). 
Introduce an optional Predicate targetAttributeFilter to control how 
grpc.target is recorded in OpenTelemetry client metrics. When a filter is 
provided, targets rejected by the predicate are normalized to &quot;other&quot; 
to reduce grpc.target metric cardinality, while accepted targets are recorded 
as-is. If no filter is set, existing behavior is preserved. This change adds a 
new Builder API on GrpcOpenTelemetry to allow applications to configure the 
filter. </p>
   </li>
   </ul>
   <p><strong>Behavior Changes</strong></p>
   <ul>
   <li>
   <p>core: Convert AutoConfiguredLB to an actual LB (4bbf8eee5). This is an 
internal refactoring, but it does improve how errors are handled for broken 
binaries. Previously, not being able to load pick_first would result in a 
channel panic. Now it is handled as a regular load balancing error</p>
   </li>
   <li>
   <p>okhttp: Assert no pending streams before transport READY (<a 
href="https://redirect.github.com/grpc/grpc-java/issues/12566";>#12566</a>) 
(ed6d175fc). No pending streams should exist when the transport transitions to 
READY. This PR adds an assertion to help verify this invariant.</p>
   </li>
   </ul>
   <p><strong>Bug Fixes</strong></p>
   <ul>
   <li>core: PickFirstLB should not return a subchannel during CONNECTING 
(228fc8ecd). Pick-first in grpc-java has behaved this way since it was created, 
and it was of no consequence. However, now there are some load balancing 
policies (mainly RLS) that will do a pick() and hope the result to be 
reasonably accurate for metrics.</li>
   </ul>
   <p><strong>Improvements</strong></p>
   <ul>
   <li>
   <p>core: Improve DEADLINE_EXCEEDED message for CallCreds delays (ead532b39). 
Previously the error message contained “buffered_nanos” and 
“waiting_for_connection” for connection delays. However, we discovered the same 
strings were also used if waiting on CallCredentials. Now you’ll see details 
like “connecting_and_lb_delay”, “call_credentials_delay”, and 
“was_still_waiting”.</p>
   </li>
   <li>
   <p>opentelemetry: Add Android API checking (a9f73f4c0). Previously we 
assumed OpenTelemetry support would not be used on Android. It did happen to be 
compatible with Android, but since OpenTelemetry does have some Android 
support, we now have a check that it remains compatible</p>
   </li>
   <li>
   <p>core: Catch Errors when calling complex config parsing code (a535ed799). 
Error (and any other Throwable) is now caught and handled when parsing 
configuration (e.g., service config, xds). This will cause such failures to be 
handled gracefully instead of panicking the channel</p>
   </li>
   <li>
   <p>core: Implement LoadBalancer.Helper.createOobChannel() with the internals 
of createResolvingOobChannel() (3915d029c). This API is only expected to be 
relevant to the gRPC-LB lookaside load balancer, and is not believed to have 
behavior changes. Out-of-band channel had been implemented with its own 
stripped-down Channel without load balancing. Reimplementing using the 
resolving oob channel makes it a full-fledged channel and reduces the burden 
when integrating new features and allows us to have a ManagedChannelBuilder to 
use with efforts like <a 
href="https://redirect.github.com/grpc/proposal/pull/529";>gRFC A110: Child 
Channel Options</a>.</p>
   </li>
   <li>
   <p>xds: Implement the proactive connection logic in RingHashLoadBalancer as 
outlined in gRFC A61 (<a 
href="https://redirect.github.com/grpc/grpc-java/issues/12596";>#12596</a>). 
Previously, the Java implementation only initialized child balancers when a 
ring-chosen endpoint was in TRANSIENT_FAILURE during a picker's pickSubchannel 
call. This PR adds the missing logic: when a child balancer reports 
TRANSIENT_FAILURE, the LoadBalancer now proactively initializes the first 
available IDLE child if no other children are currently connecting or ready.</p>
   </li>
   </ul>
   <p>This ensures a backup subchannel starts warming up immediately outside 
the RPC flow, reducing failover latency and improving overall resilience. This 
behavior was previously present but was inadvertently lost after <a 
href="https://redirect.github.com/grpc/grpc-java/pull/10610";>#10610</a>.</p>
   <ul>
   <li>api: Add RFC 3986 support to DnsNameResolverProvider (<a 
href="https://redirect.github.com/grpc/grpc-java/issues/12602";>#12602</a>) 
(f65127cf7) Experimental RFC 3986 target URI parsing mode (disabled by 
default)</li>
   </ul>
   <p><strong>New Features</strong></p>
   <ul>
   <li>opentelemetry: Actual reason for the disconnects in subchannel 
metrics(6b2f7580c), completing the remaining work in <a 
href="https://redirect.github.com/grpc/proposal/pull/485/files";>gRFC A96: OTel 
metrics for Subchannels</a></li>
   </ul>
   <p><strong>Dependencies</strong> </p>
   <ul>
   <li>
   <p>protobuf: Upgrade Bazel protobuf to 33.1 (<a 
href="https://redirect.github.com/grpc/grpc-java/issues/12553";>#12553</a>) 
(b61a8f49c) and load java_proto_library from the protobuf repo (c7f3cdbc3)</p>
   </li>
   <li>
   <p>protobuf: Fix build with Bazel 9 by upgrading bazel_jar_jar and 
grpc-proto versions (<a 
href="https://redirect.github.com/grpc/grpc-java/issues/12569";>#12569</a>)</p>
   </li>
   <li>
   <p>Upgrade dependencies (<a 
href="https://redirect.github.com/grpc/grpc-java/issues/12588";>#12588</a>) 
(6422092e3) Netty to 4.1.130, error-prone annotations to 2.45.0, 
google-auth-library to 1.41.0, tomcat-embed-core9 to 9.0.113, tomcat-embed-core 
to 10.1.50, opentelemetry to 1.57.0, jetty-ee10-servlet to 12.1.5, 
jetty-http2-server to 12.1.5, google-cloud-logging to 3.23.9, google-auth to 
1.41.0, proto-google-common-protos to 2.63.2.</p>
   </li>
   </ul>
   <!-- raw HTML omitted -->
   </blockquote>
   <p>... (truncated)</p>
   </details>
   <details>
   <summary>Commits</summary>
   <ul>
   <li><a 
href="https://github.com/grpc/grpc-java/commit/381593f39e37b530177faad3c6035cfce4536ec7";><code>381593f</code></a>
 Bump version to 1.79.0</li>
   <li><a 
href="https://github.com/grpc/grpc-java/commit/f93ecb0ae2395d20c02b4eafe931c6796ac12598";><code>f93ecb0</code></a>
 Update README etc to reference 1.79.0</li>
   <li><a 
href="https://github.com/grpc/grpc-java/commit/f6d140f877ca11d428389b688e68e5e33f78740d";><code>f6d140f</code></a>
 xds: Normalize weights before combining endpoint and locality weights</li>
   <li><a 
href="https://github.com/grpc/grpc-java/commit/c589bef18f33c1aead47382391adba70f8bd4655";><code>c589bef</code></a>
 core: clarify dns javadoc/test about trailing path segments</li>
   <li><a 
href="https://github.com/grpc/grpc-java/commit/65596ae3a9cdf420d91748e5ad1779ad92e14627";><code>65596ae</code></a>
 core: Move 4 test cases from DnsNameResolverTest to 
DnsNameResolverProviderTe...</li>
   <li><a 
href="https://github.com/grpc/grpc-java/commit/59a64f0b685f32b70b9bf73c7e15a5b0f847f767";><code>59a64f0</code></a>
 core: Use FlagResetRule to set/restore system properties in 
DnsNameResolverTe...</li>
   <li><a 
href="https://github.com/grpc/grpc-java/commit/c5f5ee0e994f76d4edac48ea17b52a0f918af822";><code>c5f5ee0</code></a>
 opentelemetry: Add target attribute filter for metrics (<a 
href="https://redirect.github.com/grpc/grpc-java/issues/12587";>#12587</a>)</li>
   <li><a 
href="https://github.com/grpc/grpc-java/commit/f65127cf7c861a1b7cf7411ef48df6f9116d6bc3";><code>f65127c</code></a>
 api: Add RFC 3986 support to DnsNameResolverProvider (<a 
href="https://redirect.github.com/grpc/grpc-java/issues/12602";>#12602</a>)</li>
   <li><a 
href="https://github.com/grpc/grpc-java/commit/a535ed799387e41b1edb44b59907af99e770259b";><code>a535ed7</code></a>
 Catch Errors when calling complex parsing code</li>
   <li><a 
href="https://github.com/grpc/grpc-java/commit/ebb9420948e4c5ea380f9da2e1c6c0d8cf991bbe";><code>ebb9420</code></a>
 xds: Merge ClusterResolverLB into CdsLB2</li>
   <li>Additional commits viewable in <a 
href="https://github.com/grpc/grpc-java/compare/v1.78.0...v1.79.0";>compare 
view</a></li>
   </ul>
   </details>
   <br />
   
   Updates `io.grpc:grpc-alts` from 1.78.0 to 1.79.0
   <details>
   <summary>Release notes</summary>
   <p><em>Sourced from <a 
href="https://github.com/grpc/grpc-java/releases";>io.grpc:grpc-alts's 
releases</a>.</em></p>
   <blockquote>
   <h2>v1.79.0</h2>
   <p><strong>API Changes</strong></p>
   <ul>
   <li>
   <p>core: Delete the never-used 
io.grpc.internal.ReadableBuffer.readBytes(ByteBuffer) (<a 
href="https://redirect.github.com/grpc/grpc-java/issues/12580";>#12580</a>) 
(738782fb0). This is deeply internal and not accessible, so shouldn’t impact 
anything. However, Apache Arrow Java <a 
href="https://github.com/apache/arrow-java/blob/96156ccc2bf933c75c852ca7c04418a61f87defd/flight/flight-core/src/main/java/org/apache/arrow/flight/grpc/GetReadableBuffer.java#L44-L45";>uses
 reflection to access private fields</a>; <a 
href="https://redirect.github.com/apache/arrow-java/pull/954";>GH-939: Remove 
reflection for gRPC buffers</a> is swapping to gRPC’s public zero-copy APIs</p>
   </li>
   <li>
   <p>opentelemetry: Add target attribute filter for metrics (<a 
href="https://redirect.github.com/grpc/grpc-java/issues/12587";>#12587</a>). 
Introduce an optional Predicate targetAttributeFilter to control how 
grpc.target is recorded in OpenTelemetry client metrics. When a filter is 
provided, targets rejected by the predicate are normalized to &quot;other&quot; 
to reduce grpc.target metric cardinality, while accepted targets are recorded 
as-is. If no filter is set, existing behavior is preserved. This change adds a 
new Builder API on GrpcOpenTelemetry to allow applications to configure the 
filter. </p>
   </li>
   </ul>
   <p><strong>Behavior Changes</strong></p>
   <ul>
   <li>
   <p>core: Convert AutoConfiguredLB to an actual LB (4bbf8eee5). This is an 
internal refactoring, but it does improve how errors are handled for broken 
binaries. Previously, not being able to load pick_first would result in a 
channel panic. Now it is handled as a regular load balancing error</p>
   </li>
   <li>
   <p>okhttp: Assert no pending streams before transport READY (<a 
href="https://redirect.github.com/grpc/grpc-java/issues/12566";>#12566</a>) 
(ed6d175fc). No pending streams should exist when the transport transitions to 
READY. This PR adds an assertion to help verify this invariant.</p>
   </li>
   </ul>
   <p><strong>Bug Fixes</strong></p>
   <ul>
   <li>core: PickFirstLB should not return a subchannel during CONNECTING 
(228fc8ecd). Pick-first in grpc-java has behaved this way since it was created, 
and it was of no consequence. However, now there are some load balancing 
policies (mainly RLS) that will do a pick() and hope the result to be 
reasonably accurate for metrics.</li>
   </ul>
   <p><strong>Improvements</strong></p>
   <ul>
   <li>
   <p>core: Improve DEADLINE_EXCEEDED message for CallCreds delays (ead532b39). 
Previously the error message contained “buffered_nanos” and 
“waiting_for_connection” for connection delays. However, we discovered the same 
strings were also used if waiting on CallCredentials. Now you’ll see details 
like “connecting_and_lb_delay”, “call_credentials_delay”, and 
“was_still_waiting”.</p>
   </li>
   <li>
   <p>opentelemetry: Add Android API checking (a9f73f4c0). Previously we 
assumed OpenTelemetry support would not be used on Android. It did happen to be 
compatible with Android, but since OpenTelemetry does have some Android 
support, we now have a check that it remains compatible</p>
   </li>
   <li>
   <p>core: Catch Errors when calling complex config parsing code (a535ed799). 
Error (and any other Throwable) is now caught and handled when parsing 
configuration (e.g., service config, xds). This will cause such failures to be 
handled gracefully instead of panicking the channel</p>
   </li>
   <li>
   <p>core: Implement LoadBalancer.Helper.createOobChannel() with the internals 
of createResolvingOobChannel() (3915d029c). This API is only expected to be 
relevant to the gRPC-LB lookaside load balancer, and is not believed to have 
behavior changes. Out-of-band channel had been implemented with its own 
stripped-down Channel without load balancing. Reimplementing using the 
resolving oob channel makes it a full-fledged channel and reduces the burden 
when integrating new features and allows us to have a ManagedChannelBuilder to 
use with efforts like <a 
href="https://redirect.github.com/grpc/proposal/pull/529";>gRFC A110: Child 
Channel Options</a>.</p>
   </li>
   <li>
   <p>xds: Implement the proactive connection logic in RingHashLoadBalancer as 
outlined in gRFC A61 (<a 
href="https://redirect.github.com/grpc/grpc-java/issues/12596";>#12596</a>). 
Previously, the Java implementation only initialized child balancers when a 
ring-chosen endpoint was in TRANSIENT_FAILURE during a picker's pickSubchannel 
call. This PR adds the missing logic: when a child balancer reports 
TRANSIENT_FAILURE, the LoadBalancer now proactively initializes the first 
available IDLE child if no other children are currently connecting or ready.</p>
   </li>
   </ul>
   <p>This ensures a backup subchannel starts warming up immediately outside 
the RPC flow, reducing failover latency and improving overall resilience. This 
behavior was previously present but was inadvertently lost after <a 
href="https://redirect.github.com/grpc/grpc-java/pull/10610";>#10610</a>.</p>
   <ul>
   <li>api: Add RFC 3986 support to DnsNameResolverProvider (<a 
href="https://redirect.github.com/grpc/grpc-java/issues/12602";>#12602</a>) 
(f65127cf7) Experimental RFC 3986 target URI parsing mode (disabled by 
default)</li>
   </ul>
   <p><strong>New Features</strong></p>
   <ul>
   <li>opentelemetry: Actual reason for the disconnects in subchannel 
metrics(6b2f7580c), completing the remaining work in <a 
href="https://redirect.github.com/grpc/proposal/pull/485/files";>gRFC A96: OTel 
metrics for Subchannels</a></li>
   </ul>
   <p><strong>Dependencies</strong> </p>
   <ul>
   <li>
   <p>protobuf: Upgrade Bazel protobuf to 33.1 (<a 
href="https://redirect.github.com/grpc/grpc-java/issues/12553";>#12553</a>) 
(b61a8f49c) and load java_proto_library from the protobuf repo (c7f3cdbc3)</p>
   </li>
   <li>
   <p>protobuf: Fix build with Bazel 9 by upgrading bazel_jar_jar and 
grpc-proto versions (<a 
href="https://redirect.github.com/grpc/grpc-java/issues/12569";>#12569</a>)</p>
   </li>
   <li>
   <p>Upgrade dependencies (<a 
href="https://redirect.github.com/grpc/grpc-java/issues/12588";>#12588</a>) 
(6422092e3) Netty to 4.1.130, error-prone annotations to 2.45.0, 
google-auth-library to 1.41.0, tomcat-embed-core9 to 9.0.113, tomcat-embed-core 
to 10.1.50, opentelemetry to 1.57.0, jetty-ee10-servlet to 12.1.5, 
jetty-http2-server to 12.1.5, google-cloud-logging to 3.23.9, google-auth to 
1.41.0, proto-google-common-protos to 2.63.2.</p>
   </li>
   </ul>
   <!-- raw HTML omitted -->
   </blockquote>
   <p>... (truncated)</p>
   </details>
   <details>
   <summary>Commits</summary>
   <ul>
   <li><a 
href="https://github.com/grpc/grpc-java/commit/381593f39e37b530177faad3c6035cfce4536ec7";><code>381593f</code></a>
 Bump version to 1.79.0</li>
   <li><a 
href="https://github.com/grpc/grpc-java/commit/f93ecb0ae2395d20c02b4eafe931c6796ac12598";><code>f93ecb0</code></a>
 Update README etc to reference 1.79.0</li>
   <li><a 
href="https://github.com/grpc/grpc-java/commit/f6d140f877ca11d428389b688e68e5e33f78740d";><code>f6d140f</code></a>
 xds: Normalize weights before combining endpoint and locality weights</li>
   <li><a 
href="https://github.com/grpc/grpc-java/commit/c589bef18f33c1aead47382391adba70f8bd4655";><code>c589bef</code></a>
 core: clarify dns javadoc/test about trailing path segments</li>
   <li><a 
href="https://github.com/grpc/grpc-java/commit/65596ae3a9cdf420d91748e5ad1779ad92e14627";><code>65596ae</code></a>
 core: Move 4 test cases from DnsNameResolverTest to 
DnsNameResolverProviderTe...</li>
   <li><a 
href="https://github.com/grpc/grpc-java/commit/59a64f0b685f32b70b9bf73c7e15a5b0f847f767";><code>59a64f0</code></a>
 core: Use FlagResetRule to set/restore system properties in 
DnsNameResolverTe...</li>
   <li><a 
href="https://github.com/grpc/grpc-java/commit/c5f5ee0e994f76d4edac48ea17b52a0f918af822";><code>c5f5ee0</code></a>
 opentelemetry: Add target attribute filter for metrics (<a 
href="https://redirect.github.com/grpc/grpc-java/issues/12587";>#12587</a>)</li>
   <li><a 
href="https://github.com/grpc/grpc-java/commit/f65127cf7c861a1b7cf7411ef48df6f9116d6bc3";><code>f65127c</code></a>
 api: Add RFC 3986 support to DnsNameResolverProvider (<a 
href="https://redirect.github.com/grpc/grpc-java/issues/12602";>#12602</a>)</li>
   <li><a 
href="https://github.com/grpc/grpc-java/commit/a535ed799387e41b1edb44b59907af99e770259b";><code>a535ed7</code></a>
 Catch Errors when calling complex parsing code</li>
   <li><a 
href="https://github.com/grpc/grpc-java/commit/ebb9420948e4c5ea380f9da2e1c6c0d8cf991bbe";><code>ebb9420</code></a>
 xds: Merge ClusterResolverLB into CdsLB2</li>
   <li>Additional commits viewable in <a 
href="https://github.com/grpc/grpc-java/compare/v1.78.0...v1.79.0";>compare 
view</a></li>
   </ul>
   </details>
   <br />
   
   Updates `io.grpc:grpc-android` from 1.78.0 to 1.79.0
   <details>
   <summary>Release notes</summary>
   <p><em>Sourced from <a 
href="https://github.com/grpc/grpc-java/releases";>io.grpc:grpc-android's 
releases</a>.</em></p>
   <blockquote>
   <h2>v1.79.0</h2>
   <p><strong>API Changes</strong></p>
   <ul>
   <li>
   <p>core: Delete the never-used 
io.grpc.internal.ReadableBuffer.readBytes(ByteBuffer) (<a 
href="https://redirect.github.com/grpc/grpc-java/issues/12580";>#12580</a>) 
(738782fb0). This is deeply internal and not accessible, so shouldn’t impact 
anything. However, Apache Arrow Java <a 
href="https://github.com/apache/arrow-java/blob/96156ccc2bf933c75c852ca7c04418a61f87defd/flight/flight-core/src/main/java/org/apache/arrow/flight/grpc/GetReadableBuffer.java#L44-L45";>uses
 reflection to access private fields</a>; <a 
href="https://redirect.github.com/apache/arrow-java/pull/954";>GH-939: Remove 
reflection for gRPC buffers</a> is swapping to gRPC’s public zero-copy APIs</p>
   </li>
   <li>
   <p>opentelemetry: Add target attribute filter for metrics (<a 
href="https://redirect.github.com/grpc/grpc-java/issues/12587";>#12587</a>). 
Introduce an optional Predicate targetAttributeFilter to control how 
grpc.target is recorded in OpenTelemetry client metrics. When a filter is 
provided, targets rejected by the predicate are normalized to &quot;other&quot; 
to reduce grpc.target metric cardinality, while accepted targets are recorded 
as-is. If no filter is set, existing behavior is preserved. This change adds a 
new Builder API on GrpcOpenTelemetry to allow applications to configure the 
filter. </p>
   </li>
   </ul>
   <p><strong>Behavior Changes</strong></p>
   <ul>
   <li>
   <p>core: Convert AutoConfiguredLB to an actual LB (4bbf8eee5). This is an 
internal refactoring, but it does improve how errors are handled for broken 
binaries. Previously, not being able to load pick_first would result in a 
channel panic. Now it is handled as a regular load balancing error</p>
   </li>
   <li>
   <p>okhttp: Assert no pending streams before transport READY (<a 
href="https://redirect.github.com/grpc/grpc-java/issues/12566";>#12566</a>) 
(ed6d175fc). No pending streams should exist when the transport transitions to 
READY. This PR adds an assertion to help verify this invariant.</p>
   </li>
   </ul>
   <p><strong>Bug Fixes</strong></p>
   <ul>
   <li>core: PickFirstLB should not return a subchannel during CONNECTING 
(228fc8ecd). Pick-first in grpc-java has behaved this way since it was created, 
and it was of no consequence. However, now there are some load balancing 
policies (mainly RLS) that will do a pick() and hope the result to be 
reasonably accurate for metrics.</li>
   </ul>
   <p><strong>Improvements</strong></p>
   <ul>
   <li>
   <p>core: Improve DEADLINE_EXCEEDED message for CallCreds delays (ead532b39). 
Previously the error message contained “buffered_nanos” and 
“waiting_for_connection” for connection delays. However, we discovered the same 
strings were also used if waiting on CallCredentials. Now you’ll see details 
like “connecting_and_lb_delay”, “call_credentials_delay”, and 
“was_still_waiting”.</p>
   </li>
   <li>
   <p>opentelemetry: Add Android API checking (a9f73f4c0). Previously we 
assumed OpenTelemetry support would not be used on Android. It did happen to be 
compatible with Android, but since OpenTelemetry does have some Android 
support, we now have a check that it remains compatible</p>
   </li>
   <li>
   <p>core: Catch Errors when calling complex config parsing code (a535ed799). 
Error (and any other Throwable) is now caught and handled when parsing 
configuration (e.g., service config, xds). This will cause such failures to be 
handled gracefully instead of panicking the channel</p>
   </li>
   <li>
   <p>core: Implement LoadBalancer.Helper.createOobChannel() with the internals 
of createResolvingOobChannel() (3915d029c). This API is only expected to be 
relevant to the gRPC-LB lookaside load balancer, and is not believed to have 
behavior changes. Out-of-band channel had been implemented with its own 
stripped-down Channel without load balancing. Reimplementing using the 
resolving oob channel makes it a full-fledged channel and reduces the burden 
when integrating new features and allows us to have a ManagedChannelBuilder to 
use with efforts like <a 
href="https://redirect.github.com/grpc/proposal/pull/529";>gRFC A110: Child 
Channel Options</a>.</p>
   </li>
   <li>
   <p>xds: Implement the proactive connection logic in RingHashLoadBalancer as 
outlined in gRFC A61 (<a 
href="https://redirect.github.com/grpc/grpc-java/issues/12596";>#12596</a>). 
Previously, the Java implementation only initialized child balancers when a 
ring-chosen endpoint was in TRANSIENT_FAILURE during a picker's pickSubchannel 
call. This PR adds the missing logic: when a child balancer reports 
TRANSIENT_FAILURE, the LoadBalancer now proactively initializes the first 
available IDLE child if no other children are currently connecting or ready.</p>
   </li>
   </ul>
   <p>This ensures a backup subchannel starts warming up immediately outside 
the RPC flow, reducing failover latency and improving overall resilience. This 
behavior was previously present but was inadvertently lost after <a 
href="https://redirect.github.com/grpc/grpc-java/pull/10610";>#10610</a>.</p>
   <ul>
   <li>api: Add RFC 3986 support to DnsNameResolverProvider (<a 
href="https://redirect.github.com/grpc/grpc-java/issues/12602";>#12602</a>) 
(f65127cf7) Experimental RFC 3986 target URI parsing mode (disabled by 
default)</li>
   </ul>
   <p><strong>New Features</strong></p>
   <ul>
   <li>opentelemetry: Actual reason for the disconnects in subchannel 
metrics(6b2f7580c), completing the remaining work in <a 
href="https://redirect.github.com/grpc/proposal/pull/485/files";>gRFC A96: OTel 
metrics for Subchannels</a></li>
   </ul>
   <p><strong>Dependencies</strong> </p>
   <ul>
   <li>
   <p>protobuf: Upgrade Bazel protobuf to 33.1 (<a 
href="https://redirect.github.com/grpc/grpc-java/issues/12553";>#12553</a>) 
(b61a8f49c) and load java_proto_library from the protobuf repo (c7f3cdbc3)</p>
   </li>
   <li>
   <p>protobuf: Fix build with Bazel 9 by upgrading bazel_jar_jar and 
grpc-proto versions (<a 
href="https://redirect.github.com/grpc/grpc-java/issues/12569";>#12569</a>)</p>
   </li>
   <li>
   <p>Upgrade dependencies (<a 
href="https://redirect.github.com/grpc/grpc-java/issues/12588";>#12588</a>) 
(6422092e3) Netty to 4.1.130, error-prone annotations to 2.45.0, 
google-auth-library to 1.41.0, tomcat-embed-core9 to 9.0.113, tomcat-embed-core 
to 10.1.50, opentelemetry to 1.57.0, jetty-ee10-servlet to 12.1.5, 
jetty-http2-server to 12.1.5, google-cloud-logging to 3.23.9, google-auth to 
1.41.0, proto-google-common-protos to 2.63.2.</p>
   </li>
   </ul>
   <!-- raw HTML omitted -->
   </blockquote>
   <p>... (truncated)</p>
   </details>
   <details>
   <summary>Commits</summary>
   <ul>
   <li><a 
href="https://github.com/grpc/grpc-java/commit/381593f39e37b530177faad3c6035cfce4536ec7";><code>381593f</code></a>
 Bump version to 1.79.0</li>
   <li><a 
href="https://github.com/grpc/grpc-java/commit/f93ecb0ae2395d20c02b4eafe931c6796ac12598";><code>f93ecb0</code></a>
 Update README etc to reference 1.79.0</li>
   <li><a 
href="https://github.com/grpc/grpc-java/commit/f6d140f877ca11d428389b688e68e5e33f78740d";><code>f6d140f</code></a>
 xds: Normalize weights before combining endpoint and locality weights</li>
   <li><a 
href="https://github.com/grpc/grpc-java/commit/c589bef18f33c1aead47382391adba70f8bd4655";><code>c589bef</code></a>
 core: clarify dns javadoc/test about trailing path segments</li>
   <li><a 
href="https://github.com/grpc/grpc-java/commit/65596ae3a9cdf420d91748e5ad1779ad92e14627";><code>65596ae</code></a>
 core: Move 4 test cases from DnsNameResolverTest to 
DnsNameResolverProviderTe...</li>
   <li><a 
href="https://github.com/grpc/grpc-java/commit/59a64f0b685f32b70b9bf73c7e15a5b0f847f767";><code>59a64f0</code></a>
 core: Use FlagResetRule to set/restore system properties in 
DnsNameResolverTe...</li>
   <li><a 
href="https://github.com/grpc/grpc-java/commit/c5f5ee0e994f76d4edac48ea17b52a0f918af822";><code>c5f5ee0</code></a>
 opentelemetry: Add target attribute filter for metrics (<a 
href="https://redirect.github.com/grpc/grpc-java/issues/12587";>#12587</a>)</li>
   <li><a 
href="https://github.com/grpc/grpc-java/commit/f65127cf7c861a1b7cf7411ef48df6f9116d6bc3";><code>f65127c</code></a>
 api: Add RFC 3986 support to DnsNameResolverProvider (<a 
href="https://redirect.github.com/grpc/grpc-java/issues/12602";>#12602</a>)</li>
   <li><a 
href="https://github.com/grpc/grpc-java/commit/a535ed799387e41b1edb44b59907af99e770259b";><code>a535ed7</code></a>
 Catch Errors when calling complex parsing code</li>
   <li><a 
href="https://github.com/grpc/grpc-java/commit/ebb9420948e4c5ea380f9da2e1c6c0d8cf991bbe";><code>ebb9420</code></a>
 xds: Merge ClusterResolverLB into CdsLB2</li>
   <li>Additional commits viewable in <a 
href="https://github.com/grpc/grpc-java/compare/v1.78.0...v1.79.0";>compare 
view</a></li>
   </ul>
   </details>
   <br />
   
   Updates `io.grpc:grpc-api` from 1.78.0 to 1.79.0
   <details>
   <summary>Release notes</summary>
   <p><em>Sourced from <a 
href="https://github.com/grpc/grpc-java/releases";>io.grpc:grpc-api's 
releases</a>.</em></p>
   <blockquote>
   <h2>v1.79.0</h2>
   <p><strong>API Changes</strong></p>
   <ul>
   <li>
   <p>core: Delete the never-used 
io.grpc.internal.ReadableBuffer.readBytes(ByteBuffer) (<a 
href="https://redirect.github.com/grpc/grpc-java/issues/12580";>#12580</a>) 
(738782fb0). This is deeply internal and not accessible, so shouldn’t impact 
anything. However, Apache Arrow Java <a 
href="https://github.com/apache/arrow-java/blob/96156ccc2bf933c75c852ca7c04418a61f87defd/flight/flight-core/src/main/java/org/apache/arrow/flight/grpc/GetReadableBuffer.java#L44-L45";>uses
 reflection to access private fields</a>; <a 
href="https://redirect.github.com/apache/arrow-java/pull/954";>GH-939: Remove 
reflection for gRPC buffers</a> is swapping to gRPC’s public zero-copy APIs</p>
   </li>
   <li>
   <p>opentelemetry: Add target attribute filter for metrics (<a 
href="https://redirect.github.com/grpc/grpc-java/issues/12587";>#12587</a>). 
Introduce an optional Predicate targetAttributeFilter to control how 
grpc.target is recorded in OpenTelemetry client metrics. When a filter is 
provided, targets rejected by the predicate are normalized to &quot;other&quot; 
to reduce grpc.target metric cardinality, while accepted targets are recorded 
as-is. If no filter is set, existing behavior is preserved. This change adds a 
new Builder API on GrpcOpenTelemetry to allow applications to configure the 
filter. </p>
   </li>
   </ul>
   <p><strong>Behavior Changes</strong></p>
   <ul>
   <li>
   <p>core: Convert AutoConfiguredLB to an actual LB (4bbf8eee5). This is an 
internal refactoring, but it does improve how errors are handled for broken 
binaries. Previously, not being able to load pick_first would result in a 
channel panic. Now it is handled as a regular load balancing error</p>
   </li>
   <li>
   <p>okhttp: Assert no pending streams before transport READY (<a 
href="https://redirect.github.com/grpc/grpc-java/issues/12566";>#12566</a>) 
(ed6d175fc). No pending streams should exist when the transport transitions to 
READY. This PR adds an assertion to help verify this invariant.</p>
   </li>
   </ul>
   <p><strong>Bug Fixes</strong></p>
   <ul>
   <li>core: PickFirstLB should not return a subchannel during CONNECTING 
(228fc8ecd). Pick-first in grpc-java has behaved this way since it was created, 
and it was of no consequence. However, now there are some load balancing 
policies (mainly RLS) that will do a pick() and hope the result to be 
reasonably accurate for metrics.</li>
   </ul>
   <p><strong>Improvements</strong></p>
   <ul>
   <li>
   <p>core: Improve DEADLINE_EXCEEDED message for CallCreds delays (ead532b39). 
Previously the error message contained “buffered_nanos” and 
“waiting_for_connection” for connection delays. However, we discovered the same 
strings were also used if waiting on CallCredentials. Now you’ll see details 
like “connecting_and_lb_delay”, “call_credentials_delay”, and 
“was_still_waiting”.</p>
   </li>
   <li>
   <p>opentelemetry: Add Android API checking (a9f73f4c0). Previously we 
assumed OpenTelemetry support would not be used on Android. It did happen to be 
compatible with Android, but since OpenTelemetry does have some Android 
support, we now have a check that it remains compatible</p>
   </li>
   <li>
   <p>core: Catch Errors when calling complex config parsing code (a535ed799). 
Error (and any other Throwable) is now caught and handled when parsing 
configuration (e.g., service config, xds). This will cause such failures to be 
handled gracefully instead of panicking the channel</p>
   </li>
   <li>
   <p>core: Implement LoadBalancer.Helper.createOobChannel() with the internals 
of createResolvingOobChannel() (3915d029c). This API is only expected to be 
relevant to the gRPC-LB lookaside load balancer, and is not believed to have 
behavior changes. Out-of-band channel had been implemented with its own 
stripped-down Channel without load balancing. Reimplementing using the 
resolving oob channel makes it a full-fledged channel and reduces the burden 
when integrating new features and allows us to have a ManagedChannelBuilder to 
use with efforts like <a 
href="https://redirect.github.com/grpc/proposal/pull/529";>gRFC A110: Child 
Channel Options</a>.</p>
   </li>
   <li>
   <p>xds: Implement the proactive connection logic in RingHashLoadBalancer as 
outlined in gRFC A61 (<a 
href="https://redirect.github.com/grpc/grpc-java/issues/12596";>#12596</a>). 
Previously, the Java implementation only initialized child balancers when a 
ring-chosen endpoint was in TRANSIENT_FAILURE during a picker's pickSubchannel 
call. This PR adds the missing logic: when a child balancer reports 
TRANSIENT_FAILURE, the LoadBalancer now proactively initializes the first 
available IDLE child if no other children are currently connecting or ready.</p>
   </li>
   </ul>
   <p>This ensures a backup subchannel starts warming up immediately outside 
the RPC flow, reducing failover latency and improving overall resilience. This 
behavior was previously present but was inadvertently lost after <a 
href="https://redirect.github.com/grpc/grpc-java/pull/10610";>#10610</a>.</p>
   <ul>
   <li>api: Add RFC 3986 support to DnsNameResolverProvider (<a 
href="https://redirect.github.com/grpc/grpc-java/issues/12602";>#12602</a>) 
(f65127cf7) Experimental RFC 3986 target URI parsing mode (disabled by 
default)</li>
   </ul>
   <p><strong>New Features</strong></p>
   <ul>
   <li>opentelemetry: Actual reason for the disconnects in subchannel 
metrics(6b2f7580c), completing the remaining work in <a 
href="https://redirect.github.com/grpc/proposal/pull/485/files";>gRFC A96: OTel 
metrics for Subchannels</a></li>
   </ul>
   <p><strong>Dependencies</strong> </p>
   <ul>
   <li>
   <p>protobuf: Upgrade Bazel protobuf to 33.1 (<a 
href="https://redirect.github.com/grpc/grpc-java/issues/12553";>#12553</a>) 
(b61a8f49c) and load java_proto_library from the protobuf repo (c7f3cdbc3)</p>
   </li>
   <li>
   <p>protobuf: Fix build with Bazel 9 by upgrading bazel_jar_jar and 
grpc-proto versions (<a 
href="https://redirect.github.com/grpc/grpc-java/issues/12569";>#12569</a>)</p>
   </li>
   <li>
   <p>Upgrade dependencies (<a 
href="https://redirect.github.com/grpc/grpc-java/issues/12588";>#12588</a>) 
(6422092e3) Netty to 4.1.130, error-prone annotations to 2.45.0, 
google-auth-library to 1.41.0, tomcat-embed-core9 to 9.0.113, tomcat-embed-core 
to 10.1.50, opentelemetry to 1.57.0, jetty-ee10-servlet to 12.1.5, 
jetty-http2-server to 12.1.5, google-cloud-logging to 3.23.9, google-auth to 
1.41.0, proto-google-common-protos to 2.63.2.</p>
   </li>
   </ul>
   <!-- raw HTML omitted -->
   </blockquote>
   <p>... (truncated)</p>
   </details>
   <details>
   <summary>Commits</summary>
   <ul>
   <li><a 
href="https://github.com/grpc/grpc-java/commit/381593f39e37b530177faad3c6035cfce4536ec7";><code>381593f</code></a>
 Bump version to 1.79.0</li>
   <li><a 
href="https://github.com/grpc/grpc-java/commit/f93ecb0ae2395d20c02b4eafe931c6796ac12598";><code>f93ecb0</code></a>
 Update README etc to reference 1.79.0</li>
   <li><a 
href="https://github.com/grpc/grpc-java/commit/f6d140f877ca11d428389b688e68e5e33f78740d";><code>f6d140f</code></a>
 xds: Normalize weights before combining endpoint and locality weights</li>
   <li><a 
href="https://github.com/grpc/grpc-java/commit/c589bef18f33c1aead47382391adba70f8bd4655";><code>c589bef</code></a>
 core: clarify dns javadoc/test about trailing path segments</li>
   <li><a 
href="https://github.com/grpc/grpc-java/commit/65596ae3a9cdf420d91748e5ad1779ad92e14627";><code>65596ae</code></a>
 core: Move 4 test cases from DnsNameResolverTest to 
DnsNameResolverProviderTe...</li>
   <li><a 
href="https://github.com/grpc/grpc-java/commit/59a64f0b685f32b70b9bf73c7e15a5b0f847f767";><code>59a64f0</code></a>
 core: Use FlagResetRule to set/restore system properties in 
DnsNameResolverTe...</li>
   <li><a 
href="https://github.com/grpc/grpc-java/commit/c5f5ee0e994f76d4edac48ea17b52a0f918af822";><code>c5f5ee0</code></a>
 opentelemetry: Add target attribute filter for metrics (<a 
href="https://redirect.github.com/grpc/grpc-java/issues/12587";>#12587</a>)</li>
   <li><a 
href="https://github.com/grpc/grpc-java/commit/f65127cf7c861a1b7cf7411ef48df6f9116d6bc3";><code>f65127c</code></a>
 api: Add RFC 3986 support to DnsNameResolverProvider (<a 
href="https://redirect.github.com/grpc/grpc-java/issues/12602";>#12602</a>)</li>
   <li><a 
href="https://github.com/grpc/grpc-java/commit/a535ed799387e41b1edb44b59907af99e770259b";><code>a535ed7</code></a>
 Catch Errors when calling complex parsing code</li>
   <li><a 
href="https://github.com/grpc/grpc-java/commit/ebb9420948e4c5ea380f9da2e1c6c0d8cf991bbe";><code>ebb9420</code></a>
 xds: Merge ClusterResolverLB into CdsLB2</li>
   <li>Additional commits viewable in <a 
href="https://github.com/grpc/grpc-java/compare/v1.78.0...v1.79.0";>compare 
view</a></li>
   </ul>
   </details>
   <br />
   
   Updates `io.grpc:grpc-auth` from 1.78.0 to 1.79.0
   <details>
   <summary>Release notes</summary>
   <p><em>Sourced from <a 
href="https://github.com/grpc/grpc-java/releases";>io.grpc:grpc-auth's 
releases</a>.</em></p>
   <blockquote>
   <h2>v1.79.0</h2>
   <p><strong>API Changes</strong></p>
   <ul>
   <li>
   <p>core: Delete the never-used 
io.grpc.internal.ReadableBuffer.readBytes(ByteBuffer) (<a 
href="https://redirect.github.com/grpc/grpc-java/issues/12580";>#12580</a>) 
(738782fb0). This is deeply internal and not accessible, so shouldn’t impact 
anything. However, Apache Arrow Java <a 
href="https://github.com/apache/arrow-java/blob/96156ccc2bf933c75c852ca7c04418a61f87defd/flight/flight-core/src/main/java/org/apache/arrow/flight/grpc/GetReadableBuffer.java#L44-L45";>uses
 reflection to access private fields</a>; <a 
href="https://redirect.github.com/apache/arrow-java/pull/954";>GH-939: Remove 
reflection for gRPC buffers</a> is swapping to gRPC’s public zero-copy APIs</p>
   </li>
   <li>
   <p>opentelemetry: Add target attribute filter for metrics (<a 
href="https://redirect.github.com/grpc/grpc-java/issues/12587";>#12587</a>). 
Introduce an optional Predicate targetAttributeFilter to control how 
grpc.target is recorded in OpenTelemetry client metrics. When a filter is 
provided, targets rejected by the predicate are normalized to &quot;other&quot; 
to reduce grpc.target metric cardinality, while accepted targets are recorded 
as-is. If no filter is set, existing behavior is preserved. This change adds a 
new Builder API on GrpcOpenTelemetry to allow applications to configure the 
filter. </p>
   </li>
   </ul>
   <p><strong>Behavior Changes</strong></p>
   <ul>
   <li>
   <p>core: Convert AutoConfiguredLB to an actual LB (4bbf8eee5). This is an 
internal refactoring, but it does improve how errors are handled for broken 
binaries. Previously, not being able to load pick_first would result in a 
channel panic. Now it is handled as a regular load balancing error</p>
   </li>
   <li>
   <p>okhttp: Assert no pending streams before transport READY (<a 
href="https://redirect.github.com/grpc/grpc-java/issues/12566";>#12566</a>) 
(ed6d175fc). No pending streams should exist when the transport transitions to 
READY. This PR adds an assertion to help verify this invariant.</p>
   </li>
   </ul>
   <p><strong>Bug Fixes</strong></p>
   <ul>
   <li>core: PickFirstLB should not return a subchannel during CONNECTING 
(228fc8ecd). Pick-first in grpc-java has behaved this way since it was created, 
and it was of no consequence. However, now there are some load balancing 
policies (mainly RLS) that will do a pick() and hope the result to be 
reasonably accurate for metrics.</li>
   </ul>
   <p><strong>Improvements</strong></p>
   <ul>
   <li>
   <p>core: Improve DEADLINE_EXCEEDED message for CallCreds delays (ead532b39). 
Previously the error message contained “buffered_nanos” and 
“waiting_for_connection” for connection delays. However, we discovered the same 
strings were also used if waiting on CallCredentials. Now you’ll see details 
like “connecting_and_lb_delay”, “call_credentials_delay”, and 
“was_still_waiting”.</p>
   </li>
   <li>
   <p>opentelemetry: Add Android API checking (a9f73f4c0). Previously we 
assumed OpenTelemetry support would not be used on Android. It did happen to be 
compatible with Android, but since OpenTelemetry does have some Android 
support, we now have a check that it remains compatible</p>
   </li>
   <li>
   <p>core: Catch Errors when calling complex config parsing code (a535ed799). 
Error (and any other Throwable) is now caught and handled when parsing 
configuration (e.g., service config, xds). This will cause such failures to be 
handled gracefully instead of panicking the channel</p>
   </li>
   <li>
   <p>core: Implement LoadBalancer.Helper.createOobChannel() with the internals 
of createResolvingOobChannel() (3915d029c). This API is only expected to be 
relevant to the gRPC-LB lookaside load balancer, and is not believed to have 
behavior changes. Out-of-band channel had been implemented with its own 
stripped-down Channel without load balancing. Reimplementing using the 
resolving oob channel makes it a full-fledged channel and reduces the burden 
when integrating new features and allows us to have a ManagedChannelBuilder to 
use with efforts like <a 
href="https://redirect.github.com/grpc/proposal/pull/529";>gRFC A110: Child 
Channel Options</a>.</p>
   </li>
   <li>
   <p>xds: Implement the proactive connection logic in RingHashLoadBalancer as 
outlined in gRFC A61 (<a 
href="https://redirect.github.com/grpc/grpc-java/issues/12596";>#12596</a>). 
Previously, the Java implementation only initialized child balancers when a 
ring-chosen endpoint was in TRANSIENT_FAILURE during a picker's pickSubchannel 
call. This PR adds the missing logic: when a child balancer reports 
TRANSIENT_FAILURE, the LoadBalancer now proactively initializes the first 
available IDLE child if no other children are currently connecting or ready.</p>
   </li>
   </ul>
   <p>This ensures a backup subchannel starts warming up immediately outside 
the RPC flow, reducing failover latency and improving overall resilience. This 
behavior was previously present but was inadvertently lost after <a 
href="https://redirect.github.com/grpc/grpc-java/pull/10610";>#10610</a>.</p>
   <ul>
   <li>api: Add RFC 3986 support to DnsNameResolverProvider (<a 
href="https://redirect.github.com/grpc/grpc-java/issues/12602";>#12602</a>) 
(f65127cf7) Experimental RFC 3986 target URI parsing mode (disabled by 
default)</li>
   </ul>
   <p><strong>New Features</strong></p>
   <ul>
   <li>opentelemetry: Actual reason for the disconnects in subchannel 
metrics(6b2f7580c), completing the remaining work in <a 
href="https://redirect.github.com/grpc/proposal/pull/485/files";>gRFC A96: OTel 
metrics for Subchannels</a></li>
   </ul>
   <p><strong>Dependencies</strong> </p>
   <ul>
   <li>
   <p>protobuf: Upgrade Bazel protobuf to 33.1 (<a 
href="https://redirect.github.com/grpc/grpc-java/issues/12553";>#12553</a>) 
(b61a8f49c) and load java_proto_library from the protobuf repo (c7f3cdbc3)</p>
   </li>
   <li>
   <p>protobuf: Fix build with Bazel 9 by upgrading bazel_jar_jar and 
grpc-proto versions (<a 
href="https://redirect.github.com/grpc/grpc-java/issues/12569";>#12569</a>)</p>
   </li>
   <li>
   <p>Upgrade dependencies (<a 
href="https://redirect.github.com/grpc/grpc-java/issues/12588";>#12588</a>) 
(6422092e3) Netty to 4.1.130, error-prone annotations to 2.45.0, 
google-auth-library to 1.41.0, tomcat-embed-core9 to 9.0.113, tomcat-embed-core 
to 10.1.50, opentelemetry to 1.57.0, jetty-ee10-servlet to 12.1.5, 
jetty-http2-server to 12.1.5, google-cloud-logging to 3.23.9, google-auth to 
1.41.0, proto-google-common-protos to 2.63.2.</p>
   </li>
   </ul>
   <!-- raw HTML omitted -->
   </blockquote>
   <p>... (truncated)</p>
   </details>
   <details>
   <summary>Commits</summary>
   <ul>
   <li><a 
href="https://github.com/grpc/grpc-java/commit/381593f39e37b530177faad3c6035cfce4536ec7";><code>381593f</code></a>
 Bump version to 1.79.0</li>
   <li><a 
href="https://github.com/grpc/grpc-java/commit/f93ecb0ae2395d20c02b4eafe931c6796ac12598";><code>f93ecb0</code></a>
 Update README etc to reference 1.79.0</li>
   <li><a 
href="https://github.com/grpc/grpc-java/commit/f6d140f877ca11d428389b688e68e5e33f78740d";><code>f6d140f</code></a>
 xds: Normalize weights before combining endpoint and locality weights</li>
   <li><a 
href="https://github.com/grpc/grpc-java/commit/c589bef18f33c1aead47382391adba70f8bd4655";><code>c589bef</code></a>
 core: clarify dns javadoc/test about trailing path segments</li>
   <li><a 
href="https://github.com/grpc/grpc-java/commit/65596ae3a9cdf420d91748e5ad1779ad92e14627";><code>65596ae</code></a>
 core: Move 4 test cases from DnsNameResolverTest to 
DnsNameResolverProviderTe...</li>
   <li><a 
href="https://github.com/grpc/grpc-java/commit/59a64f0b685f32b70b9bf73c7e15a5b0f847f767";><code>59a64f0</code></a>
 core: Use FlagResetRule to set/restore system properties in 
DnsNameResolverTe...</li>
   <li><a 
href="https://github.com/grpc/grpc-java/commit/c5f5ee0e994f76d4edac48ea17b52a0f918af822";><code>c5f5ee0</code></a>
 opentelemetry: Add target attribute filter for metrics (<a 
href="https://redirect.github.com/grpc/grpc-java/issues/12587";>#12587</a>)</li>
   <li><a 
href="https://github.com/grpc/grpc-java/commit/f65127cf7c861a1b7cf7411ef48df6f9116d6bc3";><code>f65127c</code></a>
 api: Add RFC 3986 support to DnsNameResolverProvider (<a 
href="https://redirect.github.com/grpc/grpc-java/issues/12602";>#12602</a>)</li>
   <li><a 
href="https://github.com/grpc/grpc-java/commit/a535ed799387e41b1edb44b59907af99e770259b";><code>a535ed7</code></a>
 Catch Errors when calling complex parsing code</li>
   <li><a 
href="https://github.com/grpc/grpc-java/commit/ebb9420948e4c5ea380f9da2e1c6c0d8cf991bbe";><code>ebb9420</code></a>
 xds: Merge ClusterResolverLB into CdsLB2</li>
   <li>Additional commits viewable in <a 
href="https://github.com/grpc/grpc-java/compare/v1.78.0...v1.79.0";>compare 
view</a></li>
   </ul>
   </details>
   <br />
   
   Updates `io.grpc:grpc-benchmarks` from 1.78.0 to 1.79.0
   <details>
   <summary>Release notes</summary>
   <p><em>Sourced from <a 
href="https://github.com/grpc/grpc-java/releases";>io.grpc:grpc-benchmarks's 
releases</a>.</em></p>
   <blockquote>
   <h2>v1.79.0</h2>
   <p><strong>API Changes</strong></p>
   <ul>
   <li>
   <p>core: Delete the never-used 
io.grpc.internal.ReadableBuffer.readBytes(ByteBuffer) (<a 
href="https://redirect.github.com/grpc/grpc-java/issues/12580";>#12580</a>) 
(738782fb0). This is deeply internal and not accessible, so shouldn’t impact 
anything. However, Apache Arrow Java <a 
href="https://github.com/apache/arrow-java/blob/96156ccc2bf933c75c852ca7c04418a61f87defd/flight/flight-core/src/main/java/org/apache/arrow/flight/grpc/GetReadableBuffer.java#L44-L45";>uses
 reflection to access private fields</a>; <a 
href="https://redirect.github.com/apache/arrow-java/pull/954";>GH-939: Remove 
reflection for gRPC buffers</a> is swapping to gRPC’s public zero-copy APIs</p>
   </li>
   <li>
   <p>opentelemetry: Add target attribute filter for metrics (<a 
href="https://redirect.github.com/grpc/grpc-java/issues/12587";>#12587</a>). 
Introduce an optional Predicate targetAttributeFilter to control how 
grpc.target is recorded in OpenTelemetry client metrics. When a filter is 
provided, targets rejected by the predicate are normalized to &quot;other&quot; 
to reduce grpc.target metric cardinality, while accepted targets are recorded 
as-is. If no filter is set, existing behavior is preserved. This change adds a 
new Builder API on GrpcOpenTelemetry to allow applications to configure the 
filter. </p>
   </li>
   </ul>
   <p><strong>Behavior Changes</strong></p>
   <ul>
   <li>
   <p>core: Convert AutoConfiguredLB to an actual LB (4bbf8eee5). This is an 
internal refactoring, but it does improve how errors are handled for broken 
binaries. Previously, not being able to load pick_first would result in a 
channel panic. Now it is handled as a regular load balancing error</p>
   </li>
   <li>
   <p>okhttp: Assert no pending streams before transport READY (<a 
href="https://redirect.github.com/grpc/grpc-java/issues/12566";>#12566</a>) 
(ed6d175fc). No pending streams should exist when the transport transitions to 
READY. This PR adds an assertion to help verify this invariant.</p>
   </li>
   </ul>
   <p><strong>Bug Fixes</strong></p>
   <ul>
   <li>core: PickFirstLB should not return a subchannel during CONNECTING 
(228fc8ecd). Pick-first in grpc-java has behaved this way since it was created, 
and it was of no consequence. However, now there are some load balancing 
policies (mainly RLS) that will do a pick() and hope the result to be 
reasonably accurate for metrics.</li>
   </ul>
   <p><strong>Improvements</strong></p>
   <ul>
   <li>
   <p>core: Improve DEADLINE_EXCEEDED message for CallCreds delays (ead532b39). 
Previously the error message contained “buffered_nanos” and 
“waiting_for_connection” for connection delays. However, we discovered the same 
strings were also used if waiting on CallCredentials. Now you’ll see details 
like “connecting_and_lb_delay”, “call_credentials_delay”, and 
“was_still_waiting”.</p>
   </li>
   <li>
   <p>opentelemetry: Add Android API checking (a9f73f4c0). Previously we 
assumed OpenTelemetry support would not be used on Android. It did happen to be 
compatible with Android, but since OpenTelemetry does have some Android 
support, we now have a check that it remains compatible</p>
   </li>
   <li>
   <p>core: Catch Errors when calling complex config parsing code (a535ed799). 
Error (and any other Throwable) is now caught and handled when parsing 
configuration (e.g., service config, xds). This will cause such failures to be 
handled gracefully instead of panicking the channel</p>
   </li>
   <li>
   <p>core: Implement LoadBalancer.Helper.createOobChannel() with the internals 
of createResolvingOobChannel() (3915d029c). This API is only expected to be 
relevant to the gRPC-LB lookaside load balancer, and is not believed to have 
behavior changes. Out-of-band channel had been implemented with its own 
stripped-down Channel without load balancing. Reimplementing using the 
resolving oob channel makes it a full-fledged channel and reduces the burden 
when integrating new features and allows us to have a ManagedChannelBuilder to 
use with efforts like <a 
href="https://redirect.github.com/grpc/proposal/pull/529";>gRFC A110: Child 
Channel Options</a>.</p>
   </li>
   <li>
   <p>xds: Implement the proactive connection logic in RingHashLoadBalancer as 
outlined in gRFC A61 (<a 
href="https://redirect.github.com/grpc/grpc-java/issues/12596";>#12596</a>). 
Previously, the Java implementation only initialized child balancers when a 
ring-chosen endpoint was in TRANSIENT_FAILURE during a picker's pickSubchannel 
call. This PR adds the missing logic: when a child balancer reports 
TRANSIENT_FAILURE, the LoadBalancer now proactively initializes the first 
available IDLE child if no other children are currently connecting or ready.</p>
   </li>
   </ul>
   <p>This ensures a backup subchannel starts warming up immediately outside 
the RPC flow, reducing failover latency and improving overall resilience. This 
behavior was previously present but was inadvertently lost after <a 
href="https://redirect.github.com/grpc/grpc-java/pull/10610";>#10610</a>.</p>
   <ul>
   <li>api: Add RFC 3986 support to DnsNameResolverProvider (<a 
href="https://redirect.github.com/grpc/grpc-java/issues/12602";>#12602</a>) 
(f65127cf7) Experimental RFC 3986 target URI parsing mode (disabled by 
default)</li>
   </ul>
   <p><strong>New Features</strong></p>
   <ul>
   <li>opentelemetry: Actual reason for the disconnects in subchannel 
metrics(6b2f7580c), completing the remaining work in <a 
href="https://redirect.github.com/grpc/proposal/pull/485/files";>gRFC A96: OTel 
metrics for Subchannels</a></li>
   </ul>
   <p><strong>Dependencies</strong> </p>
   <ul>
   <li>
   <p>protobuf: Upgrade Bazel protobuf to 33.1 (<a 
href="https://redirect.github.com/grpc/grpc-java/issues/12553";>#12553</a>) 
(b61a8f49c) and load java_proto_library from the protobuf repo (c7f3cdbc3)</p>
   </li>
   <li>
   <p>protobuf: Fix build with Bazel 9 by upgrading bazel_jar_jar and 
grpc-proto versions (<a 
href="https://redirect.github.com/grpc/grpc-java/issues/12569";>#12569</a>)</p>
   </li>
   <li>
   <p>Upgrade dependencies (<a 
href="https://redirect.github.com/grpc/grpc-java/issues/12588";>#12588</a>) 
(6422092e3) Netty to 4.1.130, error-prone annotations to 2.45.0, 
google-auth-library to 1.41.0, tomcat-embed-core9 to 9.0.113, tomcat-embed-core 
to 10.1.50, opentelemetry to 1.57.0, jetty-ee10-servlet to 12.1.5, 
jetty-http2-server to 12.1.5, google-cloud-logging to 3.23.9, google-auth to 
1.41.0, proto-google-common-protos to 2.63.2.</p>
   </li>
   </ul>
   <!-- raw HTML omitted -->
   </blockquote>
   <p>... (truncated)</p>
   </details>
   <details>
   <summary>Commits</summary>
   <ul>
   <li><a 
href="https://github.com/grpc/grpc-java/commit/381593f39e37b530177faad3c6035cfce4536ec7";><code>381593f</code></a>
 Bump version to 1.79.0</li>
   <li><a 
href="https://github.com/grpc/grpc-java/commit/f93ecb0ae2395d20c02b4eafe931c6796ac12598";><code>f93ecb0</code></a>
 Update README etc to reference 1.79.0</li>
   <li><a 
href="https://github.com/grpc/grpc-java/commit/f6d140f877ca11d428389b688e68e5e33f78740d";><code>f6d140f</code></a>
 xds: Normalize weights before combining endpoint and locality weights</li>
   <li><a 
href="https://github.com/grpc/grpc-java/commit/c589bef18f33c1aead47382391adba70f8bd4655";><code>c589bef</code></a>
 core: clarify dns javadoc/test about trailing path segments</li>
   <li><a 
href="https://github.com/grpc/grpc-java/commit/65596ae3a9cdf420d91748e5ad1779ad92e14627";><code>65596ae</code></a>
 core: Move 4 test cases from DnsNameResolverTest to 
DnsNameResolverProviderTe...</li>
   <li><a 
href="https://github.com/grpc/grpc-java/commit/59a64f0b685f32b70b9bf73c7e15a5b0f847f767";><code>59a64f0</code></a>
 core: Use FlagResetRule to set/restore system properties in 
DnsNameResolverTe...</li>
   <li><a 
href="https://github.com/grpc/grpc-java/commit/c5f5ee0e994f76d4edac48ea17b52a0f918af822";><code>c5f5ee0</code></a>
 opentelemetry: Add target attribute filter for metrics (<a 
href="https://redirect.github.com/grpc/grpc-java/issues/12587";>#12587</a>)</li>
   <li><a 
href="https://github.com/grpc/grpc-java/commit/f65127cf7c861a1b7cf7411ef48df6f9116d6bc3";><code>f65127c</code></a>
 api: Add RFC 3986 support to DnsNameResolverProvider (<a 
href="https://redirect.github.com/grpc/grpc-java/issues/12602";>#12602</a>)</li>
   <li><a 
href="https://github.com/grpc/grpc-java/commit/a535ed799387e41b1edb44b59907af99e770259b";><code>a535ed7</code></a>
 Catch Errors when calling complex parsing code</li>
   <li><a 
href="https://github.com/grpc/grpc-java/commit/ebb9420948e4c5ea380f9da2e1c6c0d8cf991bbe";><code>ebb9420</code></a>
 xds: Merge ClusterResolverLB into CdsLB2</li>
   <li>Additional commits viewable in <a 
href="https://github.com/grpc/grpc-java/compare/v1.78.0...v1.79.0";>compare 
view</a></li>
   </ul>
   </details>
   <br />
   
   Updates `io.grpc:grpc-binder` from 1.78.0 to 1.79.0
   <details>
   <summary>Release notes</summary>
   <p><em>Sourced from <a 
href="https://github.com/grpc/grpc-java/releases";>io.grpc:grpc-binder's 
releases</a>.</em></p>
   <blockquote>
   <h2>v1.79.0</h2>
   <p><strong>API Changes</strong></p>
   <ul>
   <li>
   <p>core: Delete the never-used 
io.grpc.internal.ReadableBuffer.readBytes(ByteBuffer) (<a 
href="https://redirect.github.com/grpc/grpc-java/issues/12580";>#12580</a>) 
(738782fb0). This is deeply internal and not accessible, so shouldn’t impact 
anything. However, Apache Arrow Java <a 
href="https://github.com/apache/arrow-java/blob/96156ccc2bf933c75c852ca7c04418a61f87defd/flight/flight-core/src/main/java/org/apache/arrow/flight/grpc/GetReadableBuffer.java#L44-L45";>uses
 reflection to access private fields</a>; <a 
href="https://redirect.github.com/apache/arrow-java/pull/954";>GH-939: Remove 
reflection for gRPC buffers</a> is swapping to gRPC’s public zero-copy APIs</p>
   </li>
   <li>
   <p>opentelemetry: Add target attribute filter for metrics (<a 
href="https://redirect.github.com/grpc/grpc-java/issues/12587";>#12587</a>). 
Introduce an optional Predicate targetAttributeFilter to control how 
grpc.target is recorded in OpenTelemetry client metrics. When a filter is 
provided, targets rejected by the predicate are normalized to &quot;other&quot; 
to reduce grpc.target metric cardinality, while accepted targets are recorded 
as-is. If no filter is set, existing behavior is preserved. This change adds a 
new Builder API on GrpcOpenTelemetry to allow applications to configure the 
filter. </p>
   </li>
   </ul>
   <p><strong>Behavior Changes</strong></p>
   <ul>
   <li>
   <p>core: Convert AutoConfiguredLB to an actual LB (4bbf8eee5). This is an 
internal refactoring, but it does improve how errors are handled for broken 
binaries. Previously, not being able to load pick_first would result in a 
channel panic. Now it is handled as a regular load balancing error</p>
   </li>
   <li>
   <p>okhttp: Assert no pending streams before transport READY (<a 
href="https://redirect.github.com/grpc/grpc-java/issues/12566";>#12566</a>) 
(ed6d175fc). No pending streams should exist when the transport transitions to 
READY. This PR adds an assertion to help verify this invariant.</p>
   </li>
   </ul>
   <p><strong>Bug Fixes</strong></p>
   <ul>
   <li>core: PickFirstLB should not return a subchannel during CONNECTING 
(228fc8ecd). Pick-first in grpc-java has behaved this way since it was created, 
and it was of no consequence. However, now there are some load balancing 
policies (mainly RLS) that will do a pick() and hope the result to be 
reasonably accurate for metrics.</li>
   </ul>
   <p><strong>Improvements</strong></p>
   <ul>
   <li>
   <p>core: Improve DEADLINE_EXCEEDED message for CallCreds delays (ead532b39). 
Previously the error message contained “buffered_nanos” and 
“waiting_for_connection” for connection delays. However, we discovered the same 
strings were also used if waiting on CallCredentials. Now you’ll see details 
like “connecting_and_lb_delay”, “call_credentials_delay”, and 
“was_still_waiting”.</p>
   </li>
   <li>
   <p>opentelemetry: Add Android API checking (a9f73f4c0). Previously we 
assumed OpenTelemetry support would not be used on Android. It did happen to be 
compatible with Android, but since OpenTelemetry does have some Android 
support, we now have a check that it remains compatible</p>
   </li>
   <li>
   <p>core: Catch Errors when calling complex config parsing code (a535ed799). 
Error (and any other Throwable) is now caught and handled when parsing 
configuration (e.g., service config, xds). This will cause such failures to be 
handled gracefully instead of panicking the channel</p>
   </li>
   <li>
   <p>core: Implement LoadBalancer.Helper.createOobChannel() with the internals 
of createResolvingOobChannel() (3915d029c). This API is only expected to be 
relevant to the gRPC-LB lookaside load balancer, and is not believed to have 
behavior changes. Out-of-band channel had been implemented with its own 
stripped-down Channel without load balancing. Reimplementing using the 
resolving oob channel makes it a full-fledged channel and reduces the burden 
when integrating new features and allows us to have a ManagedChannelBuilder to 
use with efforts like <a 
href="https://redirect.github.com/grpc/proposal/pull/529";>gRFC A110: Child 
Channel Options</a>.</p>
   </li>
   <li>
   <p>xds: Implement the proactive connection logic in RingHashLoadBalancer as 
outlined in gRFC A61 (<a 
href="https://redirect.github.com/grpc/grpc-java/issues/12596";>#12596</a>). 
Previously, the Java implementation only initialized child balancers when a 
ring-chosen endpoint was in TRANSIENT_FAILURE during a picker's pickSubchannel 
call. This PR adds the missing logic: when a child balancer reports 
TRANSIENT_FAILURE, the LoadBalancer now proactively initializes the first 
available IDLE child if no other children are currently connecting or ready.</p>
   </li>
   </ul>
   <p>This ensures a backup subchannel starts warming up immediately outside 
the RPC flow, reducing failover latency and improving overall resilience. This 
behavior was previously present but was inadvertently lost after <a 
href="https://redirect.github.com/grpc/grpc-java/pull/10610";>#10610</a>.</p>
   <ul>
   <li>api: Add RFC 3986 support to DnsNameResolverProvider (<a 
href="https://redirect.github.com/grpc/grpc-java/issues/12602";>#12602</a>) 
(f65127cf7) Experimental RFC 3986 target URI parsing mode (disabled by 
default)</li>
   </ul>
   <p><strong>New Features</strong></p>
   <ul>
   <li>opentelemetry: Actual reason for the disconnects in subchannel 
metrics(6b2f7580c), completing the remaining work in <a 
href="https://redirect.github.com/grpc/proposal/pull/485/files";>gRFC A96: OTel 
metrics for Subchannels</a></li>
   </ul>
   <p><strong>Dependencies</strong> </p>
   <ul>
   <li>
   <p>protobuf: Upgrade Bazel protobuf to 33.1 (<a 
href="https://redirect.github.com/grpc/grpc-java/issues/12553";>#12553</a>) 
(b61a8f49c) and load java_proto_library from the protobuf repo (c7f3cdbc3)</p>
   </li>
   <li>
   <p>protobuf: Fix build with Bazel 9 by upgrading bazel_jar_jar and 
grpc-proto versions (<a 
href="https://redirect.github.com/grpc/grpc-java/issues/12569";>#12569</a>)</p>
   </li>
   <li>
   <p>Upgrade dependencies (<a 
href="https://redirect.github.com/grpc/grpc-java/issues/12588";>#12588</a>) 
(6422092e3) Netty to 4.1.130, error-prone annotations to 2.45.0, 
google-auth-library to 1.41.0, tomcat-embed-core9 to 9.0.113, tomcat-embed-core 
to 10.1.50, opentelemetry to 1.57.0, jetty-ee10-servlet to 12.1.5, 
jetty-http2-server to 12.1.5, google-cloud-logging to 3.23.9, google-auth to 
1.41.0, proto-google-common-protos to 2.63.2.</p>
   </li>
   </ul>
   <!-- raw HTML omitted -->
   </blockquote>
   <p>... (truncated)</p>
   </details>
   <details>
   <summary>Commits</summary>
   <ul>
   <li><a 
href="https://github.com/grpc/grpc-java/commit/381593f39e37b530177faad3c6035cfce4536ec7";><code>381593f</code></a>
 Bump version to 1.79.0</li>
   <li><a 
href="https://github.com/grpc/grpc-java/commit/f93ecb0ae2395d20c02b4eafe931c6796ac12598";><code>f93ecb0</code></a>
 Update README etc to reference 1.79.0</li>
   <li><a 
href="https://github.com/grpc/grpc-java/commit/f6d140f877ca11d428389b688e68e5e33f78740d";><code>f6d140f</code></a>
 xds: Normalize weights before combining endpoint and locality weights</li>
   <li><a 
href="https://github.com/grpc/grpc-java/commit/c589bef18f33c1aead47382391adba70f8bd4655";><code>c589bef</code></a>
 core: clarify dns javadoc/test about trailing path segments</li>
   <li><a 
href="https://github.com/grpc/grpc-java/commit/65596ae3a9cdf420d91748e5ad1779ad92e14627";><code>65596ae</code></a>
 core: Move 4 test cases from DnsNameResolverTest to 
DnsNameResolverProviderTe...</li>
   <li><a 
href="https://github.com/grpc/grpc-java/commit/59a64f0b685f32b70b9bf73c7e15a5b0f847f767";><code>59a64f0</code></a>
 core: Use FlagResetRule to set/restore system properties in 
DnsNameResolverTe...</li>
   <li><a 
href="https://github.com/grpc/grpc-java/commit/c5f5ee0e994f76d4edac48ea17b52a0f918af822";><code>c5f5ee0</code></a>
 opentelemetry: Add target attribute filter for metrics (<a 
href="https://redirect.github.com/grpc/grpc-java/issues/12587";>#12587</a>)</li>
   <li><a 
href="https://github.com/grpc/grpc-java/commit/f65127cf7c861a1b7cf7411ef48df6f9116d6bc3";><code>f65127c</code></a>
 api: Add RFC 3986 support to DnsNameResolverProvider (<a 
href="https://redirect.github.com/grpc/grpc-java/issues/12602";>#12602</a>)</li>
   <li><a 
href="https://github.com/grpc/grpc-java/commit/a535ed799387e41b1edb44b59907af99e770259b";><code>a535ed7</code></a>
 Catch Errors when calling complex parsing code</li>
   <li><a 
href="https://github.com/grpc/grpc-java/commit/ebb9420948e4c5ea380f9da2e1c6c0d8cf991bbe";><code>ebb9420</code></a>
 xds: Merge ClusterResolverLB into CdsLB2</li>
   <li>Additional commits viewable in <a 
href="https://github.com/grpc/grpc-java/compare/v1.78.0...v1.79.0";>compare 
view</a></li>
   </ul>
   </details>
   <br />
   
   Updates `io.grpc:grpc-census` from 1.78.0 to 1.79.0
   <details>
   <summary>Release notes</summary>
   <p><em>Sourced from <a 
href="https://github.com/grpc/grpc-java/releases";>io.grpc:grpc-census's 
releases</a>.</em></p>
   <blockquote>
   <h2>v1.79.0</h2>
   <p><strong>API Changes</strong></p>
   <ul>
   <li>
   <p>core: Delete the never-used 
io.grpc.internal.ReadableBuffer.readBytes(ByteBuffer) (<a 
href="https://redirect.github.com/grpc/grpc-java/issues/12580";>#12580</a>) 
(738782fb0). This is deeply internal and not accessible, so shouldn’t impact 
anything. However, Apache Arrow Java <a 
href="https://github.com/apache/arrow-java/blob/96156ccc2bf933c75c852ca7c04418a61f87defd/flight/flight-core/src/main/java/org/apache/arrow/flight/grpc/GetReadableBuffer.java#L44-L45";>uses
 reflection to access private fields</a>; <a 
href="https://redirect.github.com/apache/arrow-java/pull/954";>GH-939: Remove 
reflection for gRPC buffers</a> is swapping to gRPC’s public zero-copy APIs</p>
   </li>
   <li>
   <p>opentelemetry: Add target attribute filter for metrics (<a 
href="https://redirect.github.com/grpc/grpc-java/issues/12587";>#12587</a>). 
Introduce an optional Predicate targetAttributeFilter to control how 
grpc.target is recorded in OpenTelemetry client metrics. When a filter is 
provided, targets rejected by the predicate are normalized to &quot;other&quot; 
to reduce grpc.target metric cardinality, while accepted targets are recorded 
as-is. If no filter is set, existing behavior is preserved. This change adds a 
new Builder API on GrpcOpenTelemetry to allow applications to configure the 
filter. </p>
   </li>
   </ul>
   <p><strong>Behavior Changes</strong></p>
   <ul>
   <li>
   <p>core: Convert AutoConfiguredLB to an actual LB (4bbf8eee5). This is an 
internal refactoring, but it does improve how errors are handled for broken 
binaries. Previously, not being able to load pick_first would result in a 
channel panic. Now it is handled as a regular load balancing error</p>
   </li>
   <li>
   <p>okhttp: Assert no pending streams before transport READY (<a 
href="https://redirect.github.com/grpc/grpc-java/issues/12566";>#12566</a>) 
(ed6d175fc). No pending streams should exist when the transport transitions to 
READY. This PR adds an assertion to help verify this invariant.</p>
   </li>
   </ul>
   <p><strong>Bug Fixes</strong></p>
   <ul>
   <li>core: PickFirstLB should not return a subchannel during CONNECTING 
(228fc8ecd). Pick-first in grpc-java has behaved this way since it was created, 
and it was of no consequence. However, now there are some load balancing 
policies (mainly RLS) that will do a pick() and hope the result to be 
reasonably accurate for metrics.</li>
   </ul>
   <p><strong>Improvements</strong></p>
   <ul>
   <li>
   <p>core: Improve DEADLINE_EXCEEDED message for CallCreds delays (ead532b39). 
Previously the error message contained “buffered_nanos” and 
“waiting_for_connection” for connection delays. However, we discovered the same 
strings were also used if waiting on CallCredentials. Now you’ll see details 
like “connecting_and_lb_delay”, “call_credentials_delay”, and 
“was_still_waiting”.</p>
   </li>
   <li>
   <p>opentelemetry: Add Android API checking (a9f73f4c0). Previously we 
assumed OpenTelemetry support would not be used on Android. It did happen to be 
compatible with Android, but since OpenTelemetry does have some Android 
support, we now have a check that it remains compatible</p>
   </li>
   <li>
   <p>core: Catch Errors when calling complex config parsing code (a535ed799). 
Error (and any other Throwable) is now caught and handled when parsing 
configuration (e.g., service config, xds). This will cause such failures to be 
handled gracefully instead of panicking the channel</p>
   </li>
   <li>
   <p>core: Implement LoadBalancer.Helper.createOobChannel() with t...
   
   _Description has been truncated_


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to