Process completed with exit code 3.

zapai.fieldStringer calls x509.HostnameError.Error

example.main calls http.ListenAndServe, which eventually calls x509.Certificate.VerifyHostname

example.main calls http.ListenAndServe, which eventually calls x509.Certificate.Verify

example.main calls http.ListenAndServe, which eventually calls textproto.Reader.ReadMIMEHeader

Process completed with exit code 3.

azure.main calls verflag.PrintAndExitIfRequested, which eventually calls x509.HostnameError.Error

Process completed with exit code 3.

hash.Checksums.Check calls fmt.Sprintf, which eventually calls x509.HostnameError.Error

azure.main calls core.pods.List, which eventually calls http2.unencryptedTransport.RoundTrip

azure.main calls core.pods.List, which eventually calls http2.noDialH2RoundTripper.RoundTrip

azure.main calls core.pods.List, which eventually calls http2.Transport.RoundTrip

azure.main calls core.pods.List, which eventually calls http2.Transport.NewClientConn

azure.main calls core.pods.List, which eventually calls idna.ToASCII

azure.printMigrationSummary calls fmt.Sprintf, which eventually calls x509.HostnameError.Error

azure.main calls fmt.Printf, which eventually calls x509.Certificate.VerifyHostname

azure.main calls fmt.Printf, which eventually calls x509.Certificate.Verify

azure.main calls core.pods.List, which eventually calls mime.WordDecoder.DecodeHeader

azure.main calls metrics.CreateTelemetryHandle, which eventually calls textproto.Reader.ReadMIMEHeader

Process completed with exit code 3.

azure.IPAMPlugin.CmdAdd calls client.Client.RequestIPAddress, which eventually calls http2.unencryptedTransport.RoundTrip

azure.IPAMPlugin.CmdAdd calls client.Client.RequestIPAddress, which eventually calls http2.noDialH2RoundTripper.RoundTrip

azure.IPAMPlugin.CmdAdd calls client.Client.RequestIPAddress, which eventually calls http2.Transport.RoundTrip

azure.IPAMPlugin.CmdAdd calls client.Client.RequestIPAddress, which eventually calls http2.Transport.NewClientConn

azure.IPAMPlugin.CmdAdd calls client.Client.RequestIPAddress, which eventually calls idna.ToASCII

ipconfig.ProcessIPConfigsResp calls fmt.Sprintf, which eventually calls x509.HostnameError.Error

azure.executePlugin calls zap.Logger.Debug, which eventually calls x509.Certificate.VerifyHostname

azure.executePlugin calls zap.Logger.Debug, which eventually calls x509.Certificate.Verify

azure.executePlugin calls skel.PluginMainWithError, which eventually calls textproto.Reader.ReadMIMEHeader

Process completed with exit code 3.

cilium.init calls common.init, which eventually calls x509.HostnameError.Error

cilium.init calls appinsights.init, which eventually calls x509.Certificate.VerifyHostname

cilium.init calls appinsights.init, which eventually calls x509.Certificate.Verify

cilium.init calls appinsights.init, which eventually calls textproto.Reader.ReadMIMEHeader

azure.realKubeClient.GetNode calls gentype.Client[*k8s.io/api/core/v1.Node].Get[*k8s.io/api/core/v1.Node], which eventually calls http2.unencryptedTransport.RoundTrip

azure.realKubeClient.GetNode calls gentype.Client[*k8s.io/api/core/v1.Node].Get[*k8s.io/api/core/v1.Node], which eventually calls http2.noDialH2RoundTripper.RoundTrip

azure.realKubeClient.GetNode calls gentype.Client[*k8s.io/api/core/v1.Node].Get[*k8s.io/api/core/v1.Node], which eventually calls http2.Transport.RoundTrip

azure.realKubeClient.GetNode calls gentype.Client[*k8s.io/api/core/v1.Node].Get[*k8s.io/api/core/v1.Node], which eventually calls http2.Transport.NewClientConn

azure.realKubeClient.GetNode calls gentype.Client[*k8s.io/api/core/v1.Node].Get[*k8s.io/api/core/v1.Node], which eventually calls idna.ToASCII

azure.init calls ebpf.init, which eventually calls x509.HostnameError.Error

azure.main calls verflag.PrintAndExitIfRequested, which eventually calls x509.Certificate.VerifyHostname

azure.main calls verflag.PrintAndExitIfRequested, which eventually calls x509.Certificate.Verify

azure.realKubeClient.GetNode calls gentype.Client[*k8s.io/api/core/v1.Node].Get[*k8s.io/api/core/v1.Node], which eventually calls mime.WordDecoder.DecodeHeader

azure.main calls verflag.PrintAndExitIfRequested, which eventually calls textproto.Reader.ReadMIMEHeader

Process completed with exit code 3.

ingress.init calls ebpf.init, which eventually calls x509.HostnameError.Error

kubernetes.ExecPod calls remotecommand.spdyStreamExecutor.StreamWithContext, which eventually calls spdystream.NewConnection

kubernetes.ExecPod calls remotecommand.spdyStreamExecutor.StreamWithContext, which eventually calls spdystream.Connection.Serve

kubernetes.ExecPod calls remotecommand.spdyStreamExecutor.StreamWithContext, which eventually calls spdy.NewFramer

kubernetes.ExecPod calls remotecommand.spdyStreamExecutor.StreamWithContext, which eventually calls spdy.Framer.ReadFrame

internal.WireserverTransport.RoundTrip calls http.Transport.RoundTrip, which eventually calls idna.ToASCII

restserver.HTTPRestService.UpdateEndpointHandler calls x509.HostnameError.Error

protos.dataplaneEventsClient.Connect calls grpc.clientStream.CloseSend, which eventually calls x509.Certificate.VerifyHostname

server.NPMRestServerListenAndServe calls http.Server.ListenAndServe, which eventually calls x509.Certificate.Verify

kubernetes.ExportLogsByLabelSelector calls rest.Request.Stream, which eventually calls mime.WordDecoder.DecodeHeader

client.Client.GetHTTPServiceData calls io.ReadAll, which eventually calls textproto.Reader.ReadMIMEHeader

Cannot open: File exists

Cannot open: File exists

Cannot open: File exists

Cannot open: File exists

Cannot open: File exists

Cannot open: File exists

Cannot open: File exists

Cannot open: File exists

Cannot open: File exists

Cannot open: File exists

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-go@v5.0.0. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 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 save: <h2>Our services aren't available right now</h2><p>We're working to restore all services as soon as possible. Please check back soon.</p>0Z4UfagAAAAB6oy/R7eFrRZvv30uO5q99UEhMMzBFREdFMDIxMwBFZGdl

Failed to restore: Cache service responded with 400

Both go-version and go-version-file inputs are specified, only go-version will be used

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-go@v5.0.0. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 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

Both go-version and go-version-file inputs are specified, only go-version will be used

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-go@v5.0.0. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 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

Both go-version and go-version-file inputs are specified, only go-version will be used

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-go@v5.0.0. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 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

Both go-version and go-version-file inputs are specified, only go-version will be used

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-go@v5.0.0. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 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

Both go-version and go-version-file inputs are specified, only go-version will be used

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-go@v5.0.0. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 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

Both go-version and go-version-file inputs are specified, only go-version will be used

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-go@v5.0.0. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 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

Both go-version and go-version-file inputs are specified, only go-version will be used

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-go@v5.0.0. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 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

Both go-version and go-version-file inputs are specified, only go-version will be used

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-go@v5.0.0. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 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

Both go-version and go-version-file inputs are specified, only go-version will be used

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/setup-go@v5.0.0. Actions will be forced to run with Node.js 24 by default starting June 16th, 2026. Node.js 20 will be removed from the runner on September 16th, 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

Both go-version and go-version-file inputs are specified, only go-version will be used