sourcegraph/cody

Frequent ETIMEDOUT Errors in Cody Chat

Opened this issue · 5 comments

straithate commented

Version

1.96.0

Describe the bug

I'm encountering persistent ETIMEDOUT errors with Cody Chat when using VCS, but also occurs when using Workspaces through github. The issue occurs across all models, any version of Cody (pre-release or release), and on both OSX and Windows. This also happens on multiple networks, and multiple different computers. No VPN or Firewall is configured and if something exists Sourcegraph is whitelisted.

This issue is consistent and occurs regardless of the project or codebase in use

Approximate Start Date: Since 12/12

Expected behavior

Cody Chat should work consistently without timing out.

Additional context

Log

ClientConfigSingleton failed to refresh client config: 
Error: accessing Sourcegraph HTTP API: ETIMEDOUT: timed out after 20000ms 
(https://sourcegraph.com/.api/client-config)

ModelsService new models API enabled:

codebaseRootFromMentions Failed to get repo IDs from Sourcegraph: 
Error: accessing Sourcegraph HTTP API: ETIMEDOUT: timed out after 20000ms 
(https://sourcegraph.com/.api/graphql?Repositories)

ChatController resolveContext > symf /Users/Dropbox/Projects/delivery-crew (start):

telemetry-v2 recordEvent: cody.fixup.persistence/present
PriNova commented

Hey @straithate

Thank you for reporting the issue.
The team will have a look at it.

To be clear, does an error message appear in the chat?
Does it interrupt the chat in any way because of the time out?

straithate commented

To be clear, does an error message appear in the chat? Does it interrupt the chat in any way because of the time out?

Hey @PriNova, it appears in the Output window on VCS, and when the error occurs it is impossible to use the chat or any other Cody feature as everything will just hang.

I put some further details here https://community.sourcegraph.com/t/frequent-etimedout-errors-in-cody-chat/1669/3

  • 👍2
ashleych commented

I am facing the same issue

straithate commented

I've been having more luck, but the issue still persists. I checked the Cody Network output window in VSC when this occurs and this message is being repeated:

2024-12-20 17:48:27.920 [error] { "agent": "vscode", "message": "Request Finished with Error", "protocol": "https", "timestamp": "2024-12-20T22:48:27.919Z", "timings": { "close": "2024-12-20T22:48:27.919Z", "error": "2024-12-20T22:48:27.919Z", "errorValue": { "code": "ECONNRESET", "message": "socket hang up", "stack": "Error: socket hang up\n at TLSSocket.socketCloseListener (node:_http_client:477:27)\n at TLSSocket.emit (node:events:530:35)\n at TLSSocket.emit (node:domain:489:12)\n at node:net:343:12\n at TCP.done (node:_tls_wrap:648:7)\n at TCP.callbackTrampoline (node:internal/async_hooks:130:17)" }, "socket": { "start": "2024-12-20T22:48:07.910Z" }, "start": "2024-12-20T22:48:07.906Z" }, "url": "https://sourcegraph.com/.api/graphql?ViewerPrompts" }