Cody, You Had Me at 'Hello'—But Now It's Just 'Network Error'

[GSGSDgggdzez]

Version

1.62.1

Describe the bug

I hope this message finds you well. I wanted to share my recent experience as I transitioned from using Cody AI to GitHub Copilot in VS Code. While I was excited about the new features and integration, I must admit that I feel a sense of sadness about leaving Cody behind, especially since I encountered some technical issues that I believe warrant attention.

1-Unexpected Logout: After raising my last issue, I was able to log in and use Cody without any problems. However, due to a battery issue with my computer, it powered off unexpectedly while I was coding a Go (Fiber) backend. Upon restarting, I found myself logged out of my account in VS Code.

2-Login Challenges: I faced two distinct scenarios when attempting to log back in:
Scenario 2.1- The login process initiated but became stuck in an endless loading loop. I waited for over four hours, only to be met with the same loading screen.

Scenario 2.2-Alternatively, when I did manage to log in, I received a "Network Error — Cody is unreachable" message. The OUTPUT Terminal displayed several errors, including
2025-01-27 19:36:16.111 [error] req<88>: Request Finished with Error {"agent":"vscode","error":{"code":"ETIMEDOUT","errors":[{"address":"104.18.32.187","code":"ETIMEDOUT","errno":-4039,"message":"connect ETIMEDOUT 104.18.32.187:443","port":443,"stack":"Error: connect ETIMEDOUT 104.18.32.187:443\n at createConnectionError (node:net:1652:14)\n at Timeout.internalConnectMultipleTimeout (node:net:1711:38)\n at listOnTimeout (node:internal/timers:583:11)\n at processTimers (node:internal/timers:519:7)","syscall":"connect"},{"address":"64:ff9b::ac40:9b45","code":"ENETUNREACH","errno":-4062,"message":"connect ENETUNREACH 64:ff9b::ac40:9b45:443","port":443,"stack":"Error: connect ENETUNREACH 64:ff9b::ac40:9b45:443\n at createConnectionError (node:net:1652:14)\n at afterConnectMultiple (node:net:1682:16)\n at TCPConnectWrap.callbackTrampoline (node:internal/async_hooks:130:17)","syscall":"connect"},{"address":"172.64.155.69","code":"ETIMEDOUT","errno":-4039,"message":"connect ETIMEDOUT 172.64.155.69:443","port":443,"stack":"Error: connect ETIMEDOUT 172.64.155.69:443\n at createConnectionError (node:net:1652:14)\n at Timeout.internalConnectMultipleTimeout (node:net:1711:38)\n at listOnTimeout (node:internal/timers:583:11)\n at processTimers (node:internal/timers:519:7)","syscall":"connect"},{"address":"64:ff9b::6812:20bb","code":"ENETUNREACH","errno":-4062,"message":"connect ENETUNREACH 64:ff9b::6812:20bb:443","port":443,"stack":"Error: connect ENETUNREACH 64:ff9b::6812:20bb:443\n at createConnectionError (node:net:1652:14)\n at afterConnectMultiple (node:net:1682:16)\n at TCPConnectWrap.callbackTrampoline (node:internal/async_hooks:130:17)","syscall":"connect"}],"stack":"AggregateError: \n at internalConnectMultiple (node:net:1122:18)\n at afterConnectMultiple (node:net:1689:7)\n at TCPConnectWrap.callbackTrampoline (node:internal/async_hooks:130:17)"},"protocol":"https","timeline":"start@0ms → socket@16ms → error@1898ms → close@1937ms","url":"https://cody-gateway.sourcegraph.com/-/__version"}

This indicated connectivity issues that prevented me from accessing the service.

As I reflect on this transition, I genuinely miss the functionality and support that Cody provided. I believe it’s important for the developers to be aware of these issues, as they could impact other users as well.

Thank you for your attention to this matter. I look forward to any updates or solutions that may arise.

Expected behavior

As I embarked on my journey with GitHub Copilot, I had high hopes and dreams of seamless coding bliss. I envisioned a world where my code flowed effortlessly, where suggestions appeared like magic, and where I could finally say goodbye to the endless struggle of debugging. I expected to log in smoothly, greeted by a friendly interface that would whisk me away into a realm of productivity.

Instead, I found myself in a tragicomedy of errors. The loading screen became my unwelcome companion, and the network errors felt like a cruel twist of fate. It was as if Cody AI, my once-reliable coding partner, was waving goodbye from the sidelines, leaving me with a bittersweet sense of nostalgia.

I imagined a smooth transition, where Copilot would embrace me with open arms, but instead, I was left longing for the days of Cody, reminiscing about the times we shared. I expected to dive into my coding tasks with enthusiasm, but instead, I was met with frustration and a heavy heart.

In short, I expected a seamless experience that would make me feel like a coding superhero, but instead, I found myself in a comedic yet sorrowful saga of technical difficulties. If only I could send a message in a bottle to Cody, letting it know how much I miss our coding adventures together!

Additional context

No response

[linear]

BUGS-1234 Cody, You Had Me at 'Hello'—But Now It's Just 'Network Error'

[PriNova]

Hey @GSGSDgggdzez

Thank you for your detailed report. I have some questions to pinpoint the issue.
Are you using VS Code directly in Windows or is this behavior caused in WSL?

It seems to me that a network/firewall setting or Anitvirus software is blocking the login process.

[GSGSDgggdzez]

Hey @PriNova

yes i am using Docker WSL for my day to day development
and i am on windows 11 with windows security constantly active

and if these is the problem i, i am force to use docker to develop my software

[PriNova]

@GSGSDgggdzez We could narrow down the issue. It might be related to WSL namespace configuration settings.

Are other apps able to access the network in your WSL instance?
Do your firewall settings allow network traffic through WSL/Docker?

Could be that you need additional steps to configure your WSL DNS namespace. Especially deactivating IPv6 for the WSL connection.
Some explanations and set-ups you can find here: microsoft/vscode-copilot-release#1577 (comment)