client: process RPC stats/tracing only when a handler is configured by mbissa · Pull Request #8874 · grpc/grpc-go

mbissa · 2026-02-02T11:29:24Z

This resolves an issue where below log statement keeps printing repeatedly:
"ERROR: [otel-plugin] ctx passed into client side stats handler metrics event handling has no client attempt data present".
When new stream is created for health/orca producers, stats and tracing is not setup. However, this fact is ignored during RPC and an error logs is printed to denote that stats cannot be handled. We will enable stream to have its own reference to the stats handler and only process per RPC implementation when it is present (like in case of regular data streams).

Internal issue: b/385685802

RELEASE NOTES:

stats: only process RPC stats/tracing in health and ORCA producers if a handler is configured, preventing unnecessary error logging

codecov · 2026-02-02T11:32:49Z

Codecov Report

❌ Patch coverage is 60.00000% with 6 lines in your changes missing coverage. Please review.
✅ Project coverage is 80.70%. Comparing base (2c113ab) to head (942f259).
⚠️ Report is 1 commits behind head on master.

Files with missing lines	Patch %	Lines
internal/transport/http2_client.go	53.84%	0 Missing and 6 partials ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##           master    #8874      +/-   ##
==========================================
- Coverage   81.41%   80.70%   -0.72%     
==========================================
  Files         416      416              
  Lines       33429    33434       +5     
==========================================
- Hits        27216    26982     -234     
+ Misses       4660     4648      -12     
- Partials     1553     1804     +251

Files with missing lines	Coverage Δ
internal/transport/client_stream.go	`82.22% <ø> (-17.78%)`	⬇️
internal/transport/transport.go	`89.06% <ø> (-2.09%)`	⬇️
stream.go	`76.38% <100.00%> (-5.50%)`	⬇️
internal/transport/http2_client.go	`72.39% <53.84%> (-19.96%)`	⬇️

... and 23 files with indirect coverage changes

🚀 New features to boost your workflow:

❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

easwars · 2026-02-03T00:11:07Z

Curious, how did you run into this? Is there an issue for this?

easwars · 2026-02-03T00:23:07Z

When new stream is created for health/orca producers, stats and tracing is not setup

Can you please elaborate on this?

My understanding is that when the opentelemtry.DialOption is specified at channel creation time, the gRPC channel is configured with the oTel stats handler. And this is stored in the cc.statsHandler field which is what is what gets propagated to the RPC attempt struct csAttempt in newAttemptLocked(). So, this information should also be available when creating the health or ORCA stream, right? Or is it the case that statstracing should be disabled on these streams?

I think it would be good to open an issue that documents all the details and the approach taken (and why this is the preferred approach, if there are other approached available at all). Thanks.

easwars · 2026-02-03T00:12:40Z

 	}

-	s, err := as.transport.NewStream(as.ctx, as.callHdr)
+	s, err := as.transport.NewStream(as.ctx, as.callHdr, nil)


Is this how the health and ORCA streams get a nil stats handler? We want to eliminate this duplication between the regular client stream and the non-retry client stream at some point. We tried to prioritize that work for Q1, but it didn't happen. This has been a maintenance burden for a while now, and a source of hard to find bugs.

mbissa · 2026-02-10T04:24:37Z

Just did a rebase with master to fast forward my commit and address the vet-proto failure.

arjan-bal · 2026-02-10T06:13:18Z

Just FYI, no action needed. I was considering whether we'd need to pass MetricsRecorderList separately to skip metrics recording. After reviewing the code for references, I found that MetricsRecorderList is only stored in the ClientConn struct and used for subchannel metrics. Stream metrics, on the other hand, are recorded via calls to the stats handlers.

grpc-go/stats/opentelemetry/client_metrics.go

Lines 192 to 199 in d7b3f93

    
           func (h *clientMetricsHandler) HandleRPC(ctx context.Context, rs stats.RPCStats) { 
        
           	ri := getRPCInfo(ctx) 
        
           	if ri == nil { 
        
           		logger.Error("ctx passed into client side stats handler metrics event handling has no client attempt data present") 
        
           		return 
        
           	} 
        
           	h.processRPCEvent(ctx, rs, ri.ai) 
        
           }

Consequently, this change should also eliminate the error log from the OTel metrics handler as well. As before, per-call metrics will not be recorded for RPCs initiated by producers.

easwars · 2026-02-10T18:35:14Z

/gemini review

gemini-code-assist

Code Review

This pull request refactors how RPC stats and tracing are handled to resolve an issue with repetitive error logging for health and ORCA producers. The change introduces a per-stream stats.Handler, moving away from a transport-level handler for RPC events. This allows streams like those for health checks, which don't have stats configured, to bypass stats processing, thus preventing the erroneous log messages. The implementation is clean and effective: the stats.Handler is now part of the ClientStream struct and is passed during stream creation. The NewStream function signature has been updated across the transport layer, and call sites have been correctly modified. For regular RPCs, the existing stats handler is plumbed through, while for internal streams like health checks, nil is passed, correctly disabling stats for them. The changes are logical and well-executed. This is a good improvement to reduce log noise and make stats handling more precise.

easwars

Would it be possible to add a test that verifies that the offending log is not seen for health/ORCA streams?

easwars · 2026-02-10T18:56:24Z

 	headerChanClosed uint32      // set when headerChan is closed. Used to avoid closing headerChan multiple times.
 	bytesReceived    atomic.Bool // indicates whether any bytes have been received on this stream
 	unprocessed      atomic.Bool // set if the server sends a refused stream or GOAWAY including this stream
+	statsHandler     stats.Handler


Can we please add a short trailing comment explaining when this can be nil? Thanks.

easwars · 2026-02-10T18:59:33Z

 	}

-	s, err := as.transport.NewStream(as.ctx, as.callHdr)
+	s, err := as.transport.NewStream(as.ctx, as.callHdr, nil)


Can we please add a comment here as to why we are setting it to nil here, so that future readers dont have to second guess themselves.

easwars · 2026-02-10T19:00:18Z


 	// NewStream creates a Stream for an RPC.
-	NewStream(ctx context.Context, callHdr *CallHdr) (*ClientStream, error)
+	NewStream(ctx context.Context, callHdr *CallHdr, handler stats.Handler) (*ClientStream, error)


I see that a stats.Handler field is stored in the transport now. Is it required anymore at all given that the stats handler is passed at stream creation time?

We can look at all the details and address it as part of bigger cleanup - don't want to include more changes here as this is an urgent change.

…rpc#8874) This resolves an issue where below log statement keeps printing repeatedly: "ERROR: [otel-plugin] ctx passed into client side stats handler metrics event handling has no client attempt data present". When new stream is created for health/orca producers, stats and tracing is not setup. However, this fact is ignored during RPC and an error logs is printed to denote that stats cannot be handled. We will enable stream to have its own reference to the stats handler and only process per RPC implementation when it is present (like in case of regular data streams). Internal issue: b/385685802 RELEASE NOTES: * stats: only process RPC stats/tracing in health and ORCA producers if a handler is configured, preventing unnecessary error logging

Cherry picks [PR](#8874) into 1.79.x RELEASE NOTES: * stats: only process RPC stats/tracing in health and ORCA producers if a handler is configured, preventing unnecessary error logging

…rpc#8874) This resolves an issue where below log statement keeps printing repeatedly: "ERROR: [otel-plugin] ctx passed into client side stats handler metrics event handling has no client attempt data present". When new stream is created for health/orca producers, stats and tracing is not setup. However, this fact is ignored during RPC and an error logs is printed to denote that stats cannot be handled. We will enable stream to have its own reference to the stats handler and only process per RPC implementation when it is present (like in case of regular data streams). Internal issue: b/385685802 RELEASE NOTES: * stats: only process RPC stats/tracing in health and ORCA producers if a handler is configured, preventing unnecessary error logging

#3314) Bump google.golang.org/grpc from 1.56.3 to 1.79.3 in the go_modules group across 1 directory Bumps the go_modules group with 1 update in the / directory: google.golang.org/grpc. Updates google.golang.org/grpc from 1.56.3 to 1.79.3 Release notes Sourced from google.golang.org/grpc's releases. Release 1.79.3 Security server: fix an authorization bypass where malformed :path headers (missing the leading slash) could bypass path-based restricted "deny" rules in interceptors like grpc/authz. Any request with a non-canonical path is now immediately rejected with an Unimplemented error. (#8981) Release 1.79.2 Bug Fixes stats: Prevent redundant error logging in health/ORCA producers by skipping stats/tracing processing when no stats handler is configured. (grpc/grpc-go#8874) Release 1.79.1 Bug Fixes grpc: Remove the -dev suffix from the User-Agent header. (grpc/grpc-go#8902) Release 1.79.0 API Changes mem: Add experimental API SetDefaultBufferPool to change the default buffer pool. (#8806) Special Thanks: @vanja-p experimental/stats: Update MetricsRecorder to require embedding the new UnimplementedMetricsRecorder (a no-op struct) in all implementations for forward compatibility. (#8780) Behavior Changes balancer/weightedtarget: Remove handling of Addresses and only handle Endpoints in resolver updates. (#8841) New Features experimental/stats: Add support for asynchronous gauge metrics through the new AsyncMetricReporter and RegisterAsyncReporter APIs. (#8780) pickfirst: Add support for weighted random shuffling of endpoints, as described in gRFC A113. This is enabled by default, and can be turned off using the environment variable GRPC_EXPERIMENTAL_PF_WEIGHTED_SHUFFLING. (#8864) xds: Implement :authority rewriting, as specified in gRFC A81. (#8779) balancer/randomsubsetting: Implement the random_subsetting LB policy, as specified in gRFC A68. (#8650) Special Thanks: @marek-szews Bug Fixes credentials/tls: Fix a bug where the port was not stripped from the authority override before validation. (#8726) Special Thanks: @Atul1710 xds/priority: Fix a bug causing delayed failover to lower-priority clusters when a higher-priority cluster is stuck in CONNECTING state. (#8813) health: Fix a bug where health checks failed for clients using legacy compression options (WithDecompressor or RPCDecompressor). (#8765) Special Thanks: @sanki92 transport: Fix an issue where the HTTP/2 server could skip header size checks when terminating a stream early. (#8769) Special Thanks: @joybestourous server: Propagate status detail headers, if available, when terminating a stream during request header processing. (#8754) Special Thanks: @joybestourous Performance Improvements credentials/alts: Optimize read buffer alignment to reduce copies. (#8791) mem: Optimize pooling and creation of buffer objects. (#8784) transport: Reduce slice re-allocations by reserving slice capacity. (#8797) ... (truncated) Commits dda86db Change version to 1.79.3 (#8983) 72186f1 grpc: enforce strict path checking for incoming requests on the server (#8981) 97ca352 Changing version to 1.79.3-dev (#8954) 8902ab6 Change the version to release 1.79.2 (#8947) a928670 Cherry-pick #8874 to v1.79.x (#8904) 06df363 Change version to 1.79.2-dev (#8903) 782f2de Change version to 1.79.1 (#8902) 850eccb Change version to 1.79.1-dev (#8851) 765ff05 Change version to 1.79.0 (#8850) 68804be Cherry pick #8864 to v1.79.x (#8896) Additional commits viewable in compare view 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 show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency @dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself) @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself) @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself) @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions You can disable automated security fix PRs for this repo from the Security Alerts page. Reviewed-by: Anton Sidelnikov Reviewed-by: Artem Lifshits

…jo) (#12794) This PR contains the following updates: | Package | Change | [Age](https://docs.renovatebot.com/merge-confidence/) | [Confidence](https://docs.renovatebot.com/merge-confidence/) | |---|---|---|---| | [google.golang.org/grpc](https://github.com/grpc/grpc-go) | `v1.75.0` → `v1.79.3` | ![age](https://developer.mend.io/api/mc/badges/age/go/google.golang.org%2fgrpc/v1.79.3?slim=true) | ![confidence](https://developer.mend.io/api/mc/badges/confidence/go/google.golang.org%2fgrpc/v1.75.0/v1.79.3?slim=true) | --- ### gRPC-Go has an authorization bypass via missing leading slash in :path [CVE-2026-33186](https://nvd.nist.gov/vuln/detail/CVE-2026-33186) / [GHSA-p77j-4mvh-x3m3](GHSA-p77j-4mvh-x3m3) / [GO-2026-4762](https://pkg.go.dev/vuln/GO-2026-4762) <details> <summary>More information</summary> #### Details ##### Impact _What kind of vulnerability is it? Who is impacted?_ It is an **Authorization Bypass** resulting from **Improper Input Validation** of the HTTP/2 `:path` pseudo-header. The gRPC-Go server was too lenient in its routing logic, accepting requests where the `:path` omitted the mandatory leading slash (e.g., `Service/Method` instead of `/Service/Method`). While the server successfully routed these requests to the correct handler, authorization interceptors (including the official `grpc/authz` package) evaluated the raw, non-canonical path string. Consequently, "deny" rules defined using canonical paths (starting with `/`) failed to match the incoming request, allowing it to bypass the policy if a fallback "allow" rule was present. **Who is impacted?** This affects gRPC-Go servers that meet both of the following criteria: 1. They use path-based authorization interceptors, such as the official RBAC implementation in `google.golang.org/grpc/authz` or custom interceptors relying on `info.FullMethod` or `grpc.Method(ctx)`. 2. Their security policy contains specific "deny" rules for canonical paths but allows other requests by default (a fallback "allow" rule). The vulnerability is exploitable by an attacker who can send raw HTTP/2 frames with malformed `:path` headers directly to the gRPC server. ##### Patches _Has the problem been patched? What versions should users upgrade to?_ Yes, the issue has been patched. The fix ensures that any request with a `:path` that does not start with a leading slash is immediately rejected with a `codes.Unimplemented` error, preventing it from reaching authorization interceptors or handlers with a non-canonical path string. Users should upgrade to the following versions (or newer): * **v1.79.3** * The latest **master** branch. It is recommended that all users employing path-based authorization (especially `grpc/authz`) upgrade as soon as the patch is available in a tagged release. ##### Workarounds _Is there a way for users to fix or remediate the vulnerability without upgrading?_ While upgrading is the most secure and recommended path, users can mitigate the vulnerability using one of the following methods: ##### 1. Use a Validating Interceptor (Recommended Mitigation) Add an "outermost" interceptor to your server that validates the path before any other authorization logic runs: ```go func pathValidationInterceptor(ctx context.Context, req any, info *grpc.UnaryServerInfo, handler grpc.UnaryHandler) (any, error) { if info.FullMethod == "" || info.FullMethod[0] != '/' { return nil, status.Errorf(codes.Unimplemented, "malformed method name") } return handler(ctx, req) } // Ensure this is the FIRST interceptor in your chain s := grpc.NewServer( grpc.ChainUnaryInterceptor(pathValidationInterceptor, authzInterceptor), ) ``` ##### 2. Infrastructure-Level Normalization If your gRPC server is behind a reverse proxy or load balancer (such as Envoy, NGINX, or an L7 Cloud Load Balancer), ensure it is configured to enforce strict HTTP/2 compliance for pseudo-headers and reject or normalize requests where the `:path` header does not start with a leading slash. ##### 3. Policy Hardening Switch to a "default deny" posture in your authorization policies (explicitly listing all allowed paths and denying everything else) to reduce the risk of bypasses via malformed inputs. #### Severity - CVSS Score: 9.1 / 10 (Critical) - Vector String: `CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N` #### References - [https://github.com/grpc/grpc-go/security/advisories/GHSA-p77j-4mvh-x3m3](https://github.com/grpc/grpc-go/security/advisories/GHSA-p77j-4mvh-x3m3) - [https://nvd.nist.gov/vuln/detail/CVE-2026-33186](https://nvd.nist.gov/vuln/detail/CVE-2026-33186) - [https://github.com/grpc/grpc-go](https://github.com/grpc/grpc-go) This data is provided by [OSV](https://osv.dev/vulnerability/GHSA-p77j-4mvh-x3m3) and the [GitHub Advisory Database](https://github.com/github/advisory-database) ([CC-BY 4.0](https://github.com/github/advisory-database/blob/main/LICENSE.md)). </details> --- ### Authorization bypass in gRPC-Go via missing leading slash in :path in google.golang.org/grpc [CVE-2026-33186](https://nvd.nist.gov/vuln/detail/CVE-2026-33186) / [GHSA-p77j-4mvh-x3m3](GHSA-p77j-4mvh-x3m3) / [GO-2026-4762](https://pkg.go.dev/vuln/GO-2026-4762) <details> <summary>More information</summary> #### Details Authorization bypass in gRPC-Go via missing leading slash in :path in google.golang.org/grpc #### Severity Unknown #### References - [https://github.com/grpc/grpc-go/security/advisories/GHSA-p77j-4mvh-x3m3](https://github.com/grpc/grpc-go/security/advisories/GHSA-p77j-4mvh-x3m3) This data is provided by [OSV](https://osv.dev/vulnerability/GO-2026-4762) and the [Go Vulnerability Database](https://github.com/golang/vulndb) ([CC-BY 4.0](https://github.com/golang/vulndb#license)). </details> --- ### Release Notes <details> <summary>grpc/grpc-go (google.golang.org/grpc)</summary> ### [`v1.79.3`](https://github.com/grpc/grpc-go/releases/tag/v1.79.3): Release 1.79.3 [Compare Source](grpc/grpc-go@v1.79.2...v1.79.3) ### Security - server: fix an authorization bypass where malformed :path headers (missing the leading slash) could bypass path-based restricted "deny" rules in interceptors like `grpc/authz`. Any request with a non-canonical path is now immediately rejected with an `Unimplemented` error. ([#8981](grpc/grpc-go#8981)) ### [`v1.79.2`](https://github.com/grpc/grpc-go/releases/tag/v1.79.2): Release 1.79.2 [Compare Source](grpc/grpc-go@v1.79.1...v1.79.2) ### Bug Fixes - stats: Prevent redundant error logging in health/ORCA producers by skipping stats/tracing processing when no stats handler is configured. ([#8874](grpc/grpc-go#8874)) ### [`v1.79.1`](https://github.com/grpc/grpc-go/releases/tag/v1.79.1): Release 1.79.1 [Compare Source](grpc/grpc-go@v1.79.0...v1.79.1) ### Bug Fixes - grpc: Remove the `-dev` suffix from the User-Agent header. ([#8902](grpc/grpc-go#8902)) ### [`v1.79.0`](https://github.com/grpc/grpc-go/releases/tag/v1.79.0): Release 1.79.0 [Compare Source](grpc/grpc-go@v1.78.0...v1.79.0) ### API Changes - mem: Add experimental API `SetDefaultBufferPool` to change the default buffer pool. ([#8806](grpc/grpc-go#8806)) - Special Thanks: [@vanja-p](https://github.com/vanja-p) - experimental/stats: Update `MetricsRecorder` to require embedding the new `UnimplementedMetricsRecorder` (a no-op struct) in all implementations for forward compatibility. ([#8780](grpc/grpc-go#8780)) ### Behavior Changes - balancer/weightedtarget: Remove handling of `Addresses` and only handle `Endpoints` in resolver updates. ([#8841](grpc/grpc-go#8841)) ### New Features - experimental/stats: Add support for asynchronous gauge metrics through the new `AsyncMetricReporter` and `RegisterAsyncReporter` APIs. ([#8780](grpc/grpc-go#8780)) - pickfirst: Add support for weighted random shuffling of endpoints, as described in [gRFC A113](grpc/proposal#535). - This is enabled by default, and can be turned off using the environment variable `GRPC_EXPERIMENTAL_PF_WEIGHTED_SHUFFLING`. ([#8864](grpc/grpc-go#8864)) - xds: Implement `:authority` rewriting, as specified in [gRFC A81](https://github.com/grpc/proposal/blob/master/A81-xds-authority-rewriting.md). ([#8779](grpc/grpc-go#8779)) - balancer/randomsubsetting: Implement the `random_subsetting` LB policy, as specified in [gRFC A68](https://github.com/grpc/proposal/blob/master/A68-random-subsetting.md). ([#8650](grpc/grpc-go#8650)) - Special Thanks: [@marek-szews](https://github.com/marek-szews) ### Bug Fixes - credentials/tls: Fix a bug where the port was not stripped from the authority override before validation. ([#8726](grpc/grpc-go#8726)) - Special Thanks: [@Atul1710](https://github.com/Atul1710) - xds/priority: Fix a bug causing delayed failover to lower-priority clusters when a higher-priority cluster is stuck in `CONNECTING` state. ([#8813](grpc/grpc-go#8813)) - health: Fix a bug where health checks failed for clients using legacy compression options (`WithDecompressor` or `RPCDecompressor`). ([#8765](grpc/grpc-go#8765)) - Special Thanks: [@sanki92](https://github.com/sanki92) - transport: Fix an issue where the HTTP/2 server could skip header size checks when terminating a stream early. ([#8769](grpc/grpc-go#8769)) - Special Thanks: [@joybestourous](https://github.com/joybestourous) - server: Propagate status detail headers, if available, when terminating a stream during request header processing. ([#8754](grpc/grpc-go#8754)) - Special Thanks: [@joybestourous](https://github.com/joybestourous) ### Performance Improvements - credentials/alts: Optimize read buffer alignment to reduce copies. ([#8791](grpc/grpc-go#8791)) - mem: Optimize pooling and creation of `buffer` objects. ([#8784](grpc/grpc-go#8784)) - transport: Reduce slice re-allocations by reserving slice capacity. ([#8797](grpc/grpc-go#8797)) ### [`v1.78.0`](https://github.com/grpc/grpc-go/releases/tag/v1.78.0): Release 1.78.0 [Compare Source](grpc/grpc-go@v1.77.0...v1.78.0) ### Behavior Changes - client: Align URL validation with Go 1.26+ to now reject target URLs with unbracketed colons in the hostname. ([#8716](grpc/grpc-go#8716)) - Special Thanks: [@neild](https://github.com/neild) - transport/client : Return status code `Unknown` on malformed grpc-status. ([#8735](grpc/grpc-go#8735)) - - xds/resolver: - Drop previous route resources and report an error when no matching virtual host is found. - Only log LDS/RDS configuration errors following a successful update and retain the last valid resource to prevent transient failures. ([#8711](grpc/grpc-go#8711)) ### New Features - stats/otel: Add backend service label to weighted round robin metrics as part of A89. ([#8737](grpc/grpc-go#8737)) - stats/otel: Add subchannel metrics (without the disconnection reason) to eventually replace the pickfirst metrics. ([#8738](grpc/grpc-go#8738)) - client: Wait for all pending goroutines to complete when closing a graceful switch balancer. ([#8746](grpc/grpc-go#8746)) - Special Thanks: [@twz123](https://github.com/twz123) - client: Add `experimental.AcceptCompressors` so callers can restrict the `grpc-accept-encoding` header advertised for a call. ([#8718](grpc/grpc-go#8718)) - Special Thanks: [@iblancasa](https://github.com/iblancasa) ### Bug Fixes - xds: Fix a bug in `StringMatcher` where regexes would match incorrectly when ignore\_case is set to true. ([#8723](grpc/grpc-go#8723)) - client: - Change connectivity state to CONNECTING when creating the name resolver (as part of exiting IDLE). - Change connectivity state to TRANSIENT\_FAILURE if name resolver creation fails (as part of exiting IDLE). - Change connectivity state to IDLE after idle timeout expires even when current state is TRANSIENT\_FAILURE. - Fix a bug that resulted in `OnFinish` call option not being invoked for RPCs where stream creation failed. ([#8710](grpc/grpc-go#8710)) - xdsclient: Fix a race in the xdsClient that could lead to resource-not-found errors. ([#8627](grpc/grpc-go#8627)) ### Performance Improvements - mem: Round up to nearest 4KiB for pool allocations larger than 1MiB. ([#8705](grpc/grpc-go#8705)) - Special Thanks: [@cjc25](https://github.com/cjc25) ### [`v1.77.0`](https://github.com/grpc/grpc-go/releases/tag/v1.77.0): Release 1.77.0 [Compare Source](grpc/grpc-go@v1.76.0...v1.77.0) ### API Changes - mem: Replace the `Reader` interface with a struct for better performance and maintainability. ([#8669](grpc/grpc-go#8669)) ### Behavior Changes - balancer/pickfirst: Remove support for the old `pick_first` LB policy via the environment variable `GRPC_EXPERIMENTAL_ENABLE_NEW_PICK_FIRST=false`. The new `pick_first` has been the default since `v1.71.0`. ([#8672](grpc/grpc-go#8672)) ### Bug Fixes - xdsclient: Fix a race condition in the ADS stream implementation that could result in `resource-not-found` errors, causing the gRPC client channel to move to `TransientFailure`. ([#8605](grpc/grpc-go#8605)) - client: Ignore HTTP status header for gRPC streams. ([#8548](grpc/grpc-go#8548)) - client: Set a read deadline when closing a transport to prevent it from blocking indefinitely on a broken connection. ([#8534](grpc/grpc-go#8534)) - Special Thanks: [@jgold2-stripe](https://github.com/jgold2-stripe) - client: Fix a bug where default port 443 was not automatically added to addresses without a specified port when sent to a proxy. - Setting environment variable `GRPC_EXPERIMENTAL_ENABLE_DEFAULT_PORT_FOR_PROXY_TARGET=false` disables this change; please file a bug if any problems are encountered as we will remove this option soon. ([#8613](grpc/grpc-go#8613)) - balancer/pickfirst: Fix a bug where duplicate addresses were not being ignored as intended. ([#8611](grpc/grpc-go#8611)) - server: Fix a bug that caused overcounting of channelz metrics for successful and failed streams. ([#8573](grpc/grpc-go#8573)) - Special Thanks: [@hugehoo](https://github.com/hugehoo) - balancer/pickfirst: When configured, shuffle addresses in resolver updates that lack endpoints. Since gRPC automatically adds endpoints to resolver updates, this bug only affects custom LB policies that delegate to `pick_first` but don't set endpoints. ([#8610](grpc/grpc-go#8610)) - mem: Clear large buffers before re-using. ([#8670](grpc/grpc-go#8670)) ### Performance Improvements - transport: Reduce heap allocations to reduce time spent in garbage collection. ([#8624](grpc/grpc-go#8624), [#8630](grpc/grpc-go#8630), [#8639](grpc/grpc-go#8639), [#8668](grpc/grpc-go#8668)) - transport: Avoid copies when reading and writing Data frames. ([#8657](grpc/grpc-go#8657), [#8667](grpc/grpc-go#8667)) - mem: Avoid clearing newly allocated buffers. ([#8670](grpc/grpc-go#8670)) ### New Features - outlierdetection: Add metrics specified in [gRFC A91](https://github.com/grpc/proposal/blob/master/A91-outlier-detection-metrics.md). ([#8644](grpc/grpc-go#8644)) - Special Thanks: [@davinci26](https://github.com/davinci26), [@PardhuKonakanchi](https://github.com/PardhuKonakanchi) - stats/opentelemetry: Add support for optional label `grpc.lb.backend_service` in per-call metrics ([#8637](grpc/grpc-go#8637)) - xds: Add support for JWT Call Credentials as specified in [gRFC A97](https://github.com/grpc/proposal/blob/master/A97-xds-jwt-call-creds.md). Set environment variable `GRPC_EXPERIMENTAL_XDS_BOOTSTRAP_CALL_CREDS=true` to enable this feature. ([#8536](grpc/grpc-go#8536)) - Special Thanks: [@dimpavloff](https://github.com/dimpavloff) - experimental/stats: Add support for up/down counters. ([#8581](grpc/grpc-go#8581)) ### [`v1.76.0`](https://github.com/grpc/grpc-go/releases/tag/v1.76.0): Release 1.76.0 [Compare Source](grpc/grpc-go@v1.75.1...v1.76.0) ### Dependencies - Minimum supported Go version is now 1.24 ([#8509](grpc/grpc-go#8509)) - Special Thanks: [@kevinGC](https://github.com/kevinGC) ### Bug Fixes - client: Return status `INTERNAL` when a server sends zero response messages for a unary or client-streaming RPC. ([#8523](grpc/grpc-go#8523)) - client: Fail RPCs with status `INTERNAL` instead of `UNKNOWN` upon receiving http headers with status 1xx and `END_STREAM` flag set. ([#8518](grpc/grpc-go#8518)) - Special Thanks: [@vinothkumarr227](https://github.com/vinothkumarr227) - pick\_first: Fix race condition that could cause pick\_first to get stuck in `IDLE` state on backend address change. ([#8615](grpc/grpc-go#8615)) ### New Features - credentials: Add `credentials/jwt` package providing file-based JWT PerRPCCredentials (A97). ([#8431](grpc/grpc-go#8431)) - Special Thanks: [@dimpavloff](https://github.com/dimpavloff) ### Performance Improvements - client: Improve HTTP/2 header size estimate to reduce re-allocations. ([#8547](grpc/grpc-go#8547)) - encoding/proto: Avoid redundant message size calculation when marshaling. ([#8569](grpc/grpc-go#8569)) - Special Thanks: [@rs-unity](https://github.com/rs-unity) ### [`v1.75.1`](https://github.com/grpc/grpc-go/releases/tag/v1.75.1): Release 1.75.1 [Compare Source](grpc/grpc-go@v1.75.0...v1.75.1) ### Bug Fixes - transport: Fix a data race while copying headers for stats handlers in the std lib http2 server transport. ([#8519](grpc/grpc-go#8519)) - xdsclient: - Fix a data race caused while reporting load to LRS. ([#8483](grpc/grpc-go#8483)) - Fix regression preventing empty node IDs when creating an LRS client. ([#8483](grpc/grpc-go#8483)) - server: Fix a regression preventing streams from being cancelled or timed out when blocked on flow control. ([#8528](grpc/grpc-go#8528)) </details> --- ### Configuration 📅 **Schedule**: (UTC) - Branch creation - "" - Automerge - Between 12:00 AM and 03:59 AM (`* 0-3 * * *`) 🚦 **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 this update again. --- - [ ] If you want to rebase/retry this PR, check this box --- This PR has been generated by [Mend Renovate](https://github.com/renovatebot/renovate).  Reviewed-on: https://codeberg.org/forgejo/forgejo/pulls/12794 Reviewed-by: Mathieu Fenniak <mfenniak@noreply.codeberg.org>

mbissa added this to the 1.79 Release milestone Feb 2, 2026

mbissa requested a review from arjan-bal February 2, 2026 11:29

mbissa added the Type: Bug label Feb 2, 2026

mbissa requested a review from easwars February 2, 2026 11:55

mbissa assigned arjan-bal Feb 2, 2026

arjan-bal assigned easwars Feb 2, 2026

arjan-bal added the Area: Client Includes Channel/Subchannel/Streams, Connectivity States, RPC Retries, Dial/Call Options and more. label Feb 2, 2026

mbissa assigned easwars and unassigned easwars and arjan-bal Feb 2, 2026

easwars reviewed Feb 3, 2026

View reviewed changes

easwars assigned mbissa and unassigned easwars Feb 3, 2026

mbissa force-pushed the fix-spammy-stats-log-master branch from dde0677 to 734cd3c Compare February 10, 2026 04:30

mbissa assigned easwars and unassigned mbissa Feb 10, 2026

gemini-code-assist Bot reviewed Feb 10, 2026

View reviewed changes

easwars reviewed Feb 10, 2026

View reviewed changes

easwars assigned mbissa and unassigned easwars Feb 10, 2026

eshitachandwani modified the milestones: 1.79 Release, 1.80 Release Feb 12, 2026

mbissa added 2 commits February 12, 2026 17:17

fix spammy log for missing stats in health and orca streams

0270714

review comments

e5f2136

arjan-bal changed the title ~~client: process RPC stats/tracing in health and ORCA producers only if a handler is configured~~ client: process RPC stats/tracing only if a handler is configured Feb 13, 2026

arjan-bal changed the title ~~client: process RPC stats/tracing only if a handler is configured~~ client: process RPC stats/tracing only when a handler is configured Feb 13, 2026

arjan-bal modified the milestones: 1.80 Release, 1.79 Release Feb 13, 2026

mbissa merged commit 944f058 into grpc:master Feb 13, 2026
19 checks passed

mbissa mentioned this pull request Feb 13, 2026

Cherry-pick #8874 to v1.79.x #8904

Merged

lklimek mentioned this pull request Mar 11, 2026

build(deps): Bump google.golang.org/grpc from 1.79.1 to 1.79.2 dashpay/tenderdash#1279

Merged

raelga mentioned this pull request Mar 19, 2026

chore(deps): bump google.golang.org/grpc from 1.78.0 to 1.79.3 Azure/ARO-HCP#4533

Merged

2 tasks

mitchnielsen mentioned this pull request Mar 24, 2026

chore: bump google.golang.org/grpc from 1.79.1 to 1.79.3 PrefectHQ/terraform-provider-prefect#665

Merged

Conversation

mbissa commented Feb 2, 2026 • edited by arjan-bal Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

codecov Bot commented Feb 2, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Codecov Report

Uh oh!

easwars commented Feb 3, 2026

Uh oh!

easwars commented Feb 3, 2026

Uh oh!

easwars Feb 3, 2026

Choose a reason for hiding this comment

Uh oh!

mbissa commented Feb 10, 2026

Uh oh!

arjan-bal commented Feb 10, 2026

Uh oh!

easwars commented Feb 10, 2026

Uh oh!

gemini-code-assist Bot left a comment

Choose a reason for hiding this comment

Code Review

Uh oh!

easwars left a comment

Choose a reason for hiding this comment

Uh oh!

easwars Feb 10, 2026

Choose a reason for hiding this comment

Uh oh!

mbissa Feb 12, 2026

Choose a reason for hiding this comment

Uh oh!

easwars Feb 10, 2026

Choose a reason for hiding this comment

Uh oh!

mbissa Feb 12, 2026

Choose a reason for hiding this comment

Uh oh!

easwars Feb 10, 2026

Choose a reason for hiding this comment

Uh oh!

mbissa Feb 12, 2026

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

4 participants

mbissa commented Feb 2, 2026 •

edited by arjan-bal

Loading

codecov Bot commented Feb 2, 2026 •

edited

Loading