healthcheck.Check.NotifyStopped calls sync.Once.Do, which eventually calls http2.Framer.WriteGoAway

healthcheck.Check.NotifyStopped calls sync.Once.Do, which eventually calls http2.Framer.WriteContinuation

healthcheck.Check.NotifyStopped calls sync.Once.Do, which eventually calls http2.Framer.ReadFrameHeader

healthcheck.Check.NotifyStopped calls sync.Once.Do, which eventually calls http2.Framer.ReadFrameForHeader

healthcheck.Check.NotifyStopped calls sync.Once.Do, which eventually calls http2.Framer.ReadFrame

log.StructuredLogger.Debugf calls fmt.Sprintf, which eventually calls http2.FrameType.String

log.StructuredLogger.Debugf calls fmt.Sprintf, which eventually calls http2.FrameHeader.String

log.StructuredLogger.Debugf calls fmt.Sprintf, which eventually calls http2.ErrCode.String

proxy.MultiErr.Error calls http2.ConnectionError.Error

proxy.NewClient calls cloudsqlconn.NewDialer, which eventually calls http2.ConfigureTransports

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@34e114876b0b11c390a56381ad16ebd13914f8d5, actions/setup-go@40f1582b2485089dde7abd97c1529aa768e1baff, actions/setup-go@v5.0.0. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

Failed to restore: Cache service responded with 400