Exafunction / codeium

Other
200 stars 9 forks source link

Error on VS Code : `Client codeium: connection to server is erroring. Shutting down server.` #24

Closed zb81 closed 6 months ago

zb81 commented 6 months ago

Output Error

[Error - 09:50:31] Client codeium: connection to server is erroring. Shutting down server.
[Error - 09:50:31] Client codeium: connection to server is erroring. Shutting down server.
[Error - 09:50:31] Stopping server failed
Error: Client is not running and can't be stopped. It's current state is: starting
    at b.shutdown (/Users/zb/.vscode/extensions/codeium.codeium-1.6.10/dist/extension.js:2:2518208)
    at b.stop (/Users/zb/.vscode/extensions/codeium.codeium-1.6.10/dist/extension.js:2:2517789)
    at b.stop (/Users/zb/.vscode/extensions/codeium.codeium-1.6.10/dist/extension.js:2:2680077)
    at b.handleConnectionError (/Users/zb/.vscode/extensions/codeium.codeium-1.6.10/dist/extension.js:2:2524296)
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
[Error - 09:50:31] Stopping server failed
Error: Client is not running and can't be stopped. It's current state is: starting
    at b.shutdown (/Users/zb/.vscode/extensions/codeium.codeium-1.6.10/dist/extension.js:2:2518208)
    at b.stop (/Users/zb/.vscode/extensions/codeium.codeium-1.6.10/dist/extension.js:2:2517789)
    at b.stop (/Users/zb/.vscode/extensions/codeium.codeium-1.6.10/dist/extension.js:2:2680077)
    at b.handleConnectionError (/Users/zb/.vscode/extensions/codeium.codeium-1.6.10/dist/extension.js:2:2524296)
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
[Error - 09:50:31] Server initialization failed.
  Message: Pending response rejected since connection got disposed
  Code: -32097 
[Info  - 09:50:31] Connection to server got closed. Server will restart.
true
[Error - 09:50:31] codeium client: couldn't create connection to server.
  Message: Pending response rejected since connection got disposed
  Code: -32097 
[Error - 09:50:31] codeium client: couldn't create connection to server.
Error: connect ECONNREFUSED 127.0.0.1:52516
    at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1494:16)
[Error - 09:50:31] Restarting server failed
Error: connect ECONNREFUSED 127.0.0.1:52516
    at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1494:16)

VS Code version

Version: 1.85.1
Commit: 0ee08df0cf4527e40edc9aa28f4b5bd38bbff2b2
Date: 2023-12-13T09:48:16.874Z
Electron: 25.9.7
ElectronBuildId: 25551756
Chromium: 114.0.5735.289
Node.js: 18.15.0
V8: 11.4.183.29-electron.0
OS: Darwin arm64 23.2.0
ShawSpring commented 6 months ago

I‘m facing the same issue. It takes so long to Downloading Codeium language server when install the codeium extension, then the Error output appeared.

maooyer commented 6 months ago

Same issue. It looks like a language server bug. In my case, the language server log shows LSP listening on port 52112,but I cannot found server listening on listening the port

vscode log

[Info  - 00:19:17] Connection to server got closed. Server will restart.
true
[Error - 00:19:17] codeium client: couldn't create connection to server.
  Message: Pending response rejected since connection got disposed
  Code: -32097 
[Error - 00:19:17] codeium client: couldn't create connection to server.
Error: connect ECONNREFUSED 127.0.0.1:52112
    at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1494:16)
[Error - 00:19:17] Restarting server failed
Error: connect ECONNREFUSED 127.0.0.1:52112
    at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1494:16)

server log

I1215 00:19:17.454112 11004 server.go:341] Language server will attempt to listen on host 127.0.0.1
I1215 00:19:17.454306 11004 server.go:385] Language server listening on random port at 52111
I1215 00:19:17.454313 11004 server.go:387] LSP listening on random port at 52112
I1215 00:19:17.454867 11004 web_server.go:229] Chat Web Server listening at ws://127.0.0.1:52113
I1215 00:19:17.650026 11004 server.go:1741] Skipped changelog download for version 1.6.10
image
pqn commented 6 months ago

Upgrade to 1.6.11 and it should be fixed.

pqn commented 6 months ago

Oops, it appears this release failed, we're retrying it now.

pqn commented 6 months ago

Should be updated now.