portfwdserver.TunnelServer.Start calls tcpproxy.DialProxy.HandleConn, which eventually calls ssh.NewClientConn

portfwdserver.TunnelServer.Start calls tcpproxy.DialProxy.HandleConn, which eventually calls ssh.mux.SendRequest

portfwdserver.TunnelServer.Start calls tcpproxy.DialProxy.HandleConn, which eventually calls ssh.NewClientConn

portfwdserver.TunnelServer.Start calls tcpproxy.DialProxy.HandleConn, which eventually calls ssh.ParsePrivateKeyWithPassphrase

portfwdserver.TunnelServer.Start calls tcpproxy.DialProxy.HandleConn, which eventually calls ssh.ParsePrivateKey

portfwdserver.TunnelServer.Start calls tcpproxy.DialProxy.HandleConn, which eventually calls ssh.ParseKnownHosts

portfwdserver.TunnelServer.Start calls tcpproxy.DialProxy.HandleConn, which eventually calls ssh.NewClientConn

portfwdserver.TunnelServer.Start calls tcpproxy.DialProxy.HandleConn, which eventually calls ssh.NewClientConn

store.PrintInstances calls fmt.Fprintf, which calls ssh.channel.Write

portfwdserver.TunnelServer.Start calls tcpproxy.DialProxy.HandleConn, which eventually calls ssh.NewClientConn

Process completed with exit code 1.

Process completed with exit code 124.

Final attempt failed. Child_process exited with error code 124

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v4.1.1, actions/setup-go@v5.0.0. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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

Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: ls-lint/action@02e380fe8733d499cbfc9e22276de5085508a5bd. Actions will be forced to run with Node.js 24 by default starting June 2nd, 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/

Attempt 1 failed. Reason: Child_process exited with error code 1

Attempt 2 failed. Reason: Child_process exited with error code 124

Attempt 1 failed. Reason: Child_process exited with error code 124

Summary report available at: https://github.com/lima-vm/lima/actions/runs/26299823973#summary-77421818056

NOTICE: windows-2025 requests are being redirected to windows-2025-vs2026 by June 15, 2026

NOTICE: windows-2025 requests are being redirected to windows-2025-vs2026 by June 15, 2026