Exafunction / codeium

Other
229 stars 12 forks source link

[BUG] language server port file not found #54

Open FEIFEIEIAr opened 6 months ago

FEIFEIEIAr commented 6 months ago

I encountered with following problem when using codeium on VSCode and Ubuntu.

language server port file not found

And the log says,

E0416 17:15:54.294760 471330 database.go:137] Error creating table: file is not a database (1) attached stack trace -- stack trace:
 | github.com/Exafunction/Exafunction/exa/language_server/embedding_search.NewDatabase
 | exa/language_server/embedding_search/database.go:136
 | github.com/Exafunction/Exafunction/exa/language_server/embedding_search.SetUpIndexComponents
 | exa/language_server/embedding_search/search_provider.go:177
 | github.com/Exafunction/Exafunction/exa/language_server.initServers
 | exa/language_server/server.go:430
 | github.com/Exafunction/Exafunction/exa/language_server.CreateLanguageServerAndServe
 | exa/language_server/server.go:167
 | main.main
 | exa/cmd/language_server/main.go:544
 | runtime.main
 | GOROOT/src/runtime/proc.go:267
 | runtime.goexit
 | src/runtime/asm_amd64.s:1650 
Wraps: (2) file is not a database 
Error types: (1) *withstack.withStack (2) sqlite3.Error 
F0416 17:15:54.294868 471330 main.go:546] Language server failed - file is not a database 
(1) attached stack trace 
  -- stack trace:
 | github.com/Exafunction/Exafunction/exa/language_server/embedding_search.NewDatabase
 | exa/language_server/embedding_search/database.go:136
 | github.com/Exafunction/Exafunction/exa/language_server/embedding_search.SetUpIndexComponents
 | exa/language_server/embedding_search/search_provider.go:177
 | github.com/Exafunction/Exafunction/exa/language_server.initServers | exa/language_server/server.go:430
 | github.com/Exafunction/Exafunction/exa/language_server.CreateLanguageServerAndServe
 | exa/language_server/server.go:167
 | main.main
 | exa/cmd/language_server/main.go:544
 | runtime.main
 | GOROOT/src/runtime/proc.go:267
 | runtime.goexit
 | src/runtime/asm_amd64.s:1650 
Wraps: (2) file is not a database 
Error types: (1) *withstack.withStack (2) sqlite3.Error

I reinstall Codeium for times, restart VSCode for times. Above ERROR occured all the time. After I manually deleted the whole folder ~/.codeium, I can then use the codeium again.

pqn commented 6 months ago

Is your user directory an NFS mount?

FEIFEIEIAr commented 6 months ago

Is your user directory an NFS mount?

Yes

findmnt -T /home/name
TARGET SOURCE              FSTYPE OPTIONS
/home  192.168.20.11:/home nfs4

The SOURCE (192.168.20.11:/home) is ext4. And, both have the same issue.

pqn commented 6 months ago

@michaelli611 maybe we should figure out a permanent solution for this

jeffnst commented 6 months ago

i have same problem too.. language server port file not found in C:\Users\User\AppData\Local\Temp\xxxxxxx\codeium\manager after 60s .. i use vscode (version 1.88.1) in windows 11

ozanakdur commented 5 months ago

I'm facing the same issue. Is there a solution available?

error

VSCode: 1.89.1 Codeium: 1.8.45 OS: Windows 10

diviatrix commented 5 months ago

Same problem here, both pre-release and release, both vs code | dev.

Version: 1.89.1 (system setup)
Commit: dc96b837cf6bb4af9cd736aa3af08cf8279f7685
Date: 2024-05-07T05:13:33.891Z
Electron: 28.2.8
ElectronBuildId: 27744544
Chromium: 120.0.6099.291
Node.js: 18.18.2
V8: 12.0.267.19-electron.0
OS: Windows_NT x64 10.0.22631

Language server port file not found in C:\Users\azura\AppData\Local\Temp\e69f00d2-b305-4a80-896f-f3f0e454de22\codeium\manager after 60s

All codeium commands show like that image

fortenforge commented 5 months ago

Try deleting the .codeium directory in your home directory.

diviatrix commented 5 months ago

Try deleting the .codeium directory in your home directory. actually helped! Thanks

ozanakdur commented 5 months ago

Try deleting the .codeium directory in your home directory.

Deleting the C:\Users\User\ .codeium directory resolved the issue on Windows. Thank you!

zilewang7 commented 5 months ago

Try deleting the .codeium directory in your home directory.

Success in MacOS, Thanks.

therohantomar commented 4 months ago

Try deleting the .codeium directory in your home directory.

Deleting the .codeium worked for me, Thank You!!!!

jetm commented 4 months ago

Even after deleting the .codeium/ directory, the issue persists. One way to reproduce this problem is by using Codeium in different IDEs and editors. For example, if you have a NeoVim plugin (Exafunctioncodeium.nvim) downloading the Codeium binary, VS Code will fail to do the same task or to use it. Same if you combine JetBrains products with VS Code. The workaround is to only use Codeium in one editor, not in multiple editors, which is annoying :(.

lascanorussell commented 4 months ago

Try deleting the .codeium directory in your home directory.

Works for me too. Thanks!

taylordragoo commented 4 months ago

Deleting the .codeium directory on macos did not fix the issue for me, still geting a "the server aborted the pending request" error when attempting to initialize the extension in vscode.

louis4work commented 4 months ago

Deleting the .codeium directory did not work for me as well.

Here is the log: ``` I0628 12:37:35.662869 15509 proxy.go:94] proxyplease.connect> Proxy successfully established. No authentication was required. I0628 12:37:36.180047 15509 unleash.go:90] Initializing Unleash I0628 12:37:38.181216 15509 unleash.go:110] Successfully initialized Unleash E0628 12:37:38.181530 15509 unleash.go:60] Unleash error: Post "https://unleash.codeium.com/api/client/register": dial tcp 35.223.238.178:443: i/o timeout (Client.Timeout exceeded while awaiting headers) E0628 12:37:38.181592 15509 unleash.go:60] Unleash error: Get "https://unleash.codeium.com/api/client/features": context deadline exceeded (Client.Timeout exceeded while awaiting headers) E0628 12:37:38.201992 15509 client_manager.go:270] Metadata is nil when trying to refresh user JWT (VSCode) 2024-06-28 12:37:40.790 [ERROR]: Language server port file not found in /tmp/81550df6-0493-4c4e-b73b-94f405f6c60d/codeium/manager after 60s I0628 12:37:50.247394 15153 main.go:281] Failed to get random ports within 15 seconds E0628 12:37:53.265759 15153 cmd_wrapper.go:265] LanguageServer wait failed: timed out while waiting on process 15509 at 0628 12:37:53.265611, sent SIGTERM F0628 12:37:53.265854 15153 main.go:174] Exceeded maximum number of connection failures 4 (VSCode) 2024-06-28 12:37:53.281 [INFO]: Language server exited with code 1 ```
bigtree21cn commented 4 months ago

Update: After downgrade to v1.8.73, the problem resovled.

codeium is working correctly on my local machine (win10+latest VSC). It's not working in my WSL2 environment, I open vscode with "code ." command inside WSL2 ubuntu. I did delete ~/.codeium, as well as reinstalling ~/.vscode-server/ and codeium couple of times. Not working for me yet.

The error is : [ERROR]: Language server port file not found in /tmp/0fa9d6c3-7304-446a-bcac-77332b79e4a0/codeium/manager after 60s

Any hints?

louis4work commented 4 months ago

Deleting the .codeium directory did not work for me as well.

Here is the log:

I have found that this issue occurred when the codeium extension was auto updated to v1.8.73, both on my local and remote machine. When I downgrade it to v1.8.57, everthing works well. (I use vscode.)

dnquinn commented 4 months ago

Have the same problem on termux code-oss build

Addimoh commented 4 months ago

Deleting the .codeium directory did not work for me as well. Here is the log:

I have found that this issue occurred when the codeium extension was auto updated to v1.8.73, both on my local and remote machine. When I downgrade it to v1.8.57, everthing works well. (I use vscode.)

I had the same problem for over a week. Downgrading to version 1.8.57 solved the problem.

titospadini commented 4 months ago

I am still having the same problem. I have already tried to downgrade the extension version (to several different versions, including 1.8.57); to delete the .codeium folder; to completely reinstall VSCode; and, yes, believe it or not, also to format and fresh install the operating system (Windows 11 Pro with WSL Ubuntu LTS).

akbarumar88 commented 4 months ago

Try deleting the .codeium directory in your home directory.

This solution worked for me, Im using VSCode on Windows 10

haydaraliawan commented 2 months ago

I am also facing the same issue

haydaraliawan commented 2 months ago

I am also facing the same issue

The issue is resolved when i deleted all the files and folders related to codeium manually and reinstalled it.

carlosordo commented 2 months ago

Try deleting the .codeium directory in your home directory.

This works for me

BigCatGit commented 2 months ago

Success in MacOS, Thanks.

MuhammadRashid-786 commented 2 months ago

Deleting the .codeium folder from path (C:\Users\Laptop Home[may vary on your system]) worked for me

aneesarom commented 2 months ago

For MacOs you need to delete below json files and also folder contains codeium which is available in var folder(you can get the location when you hover the mouse over failed icon of codeium) and uninstall the codeium in vscode, quit the vs code and open and install the codeium worked for me

unleash-backup-codeium-extension.json unleash-repo-schema-v1-codeium-language-server.json

DKurzmann commented 1 month ago

For MacOs you need to delete below json files and also folder contains codeium which is available in var folder(you can get the location when you hover the mouse over failed icon of codeium) and uninstall the codeium in vscode, quit the vs code and open and install the codeium worked for me

unleash-backup-codeium-extension.json unleash-repo-schema-v1-codeium-language-server.json

Did not help in my case :/

Try deleting the .codeium directory in your home directory.

This worked for me :)

liushengxian commented 1 month ago

Deleting the .codeium directory not working for me.

For MacOs you need to delete below json files and also folder contains codeium which is available in var folder(you can get the location when you hover the mouse over failed icon of codeium) and uninstall the codeium in vscode, quit the vs code and open and install the codeium worked for me

unleash-backup-codeium-extension.json unleash-repo-schema-v1-codeium-language-server.json

Trying this, but where's the json files? I've delete files in val folder and reinstall codeium but not working.

geomorillo commented 3 weeks ago

Deleting .codeium doesnt work for me on windows 10

AEAQA commented 2 weeks ago

Try deleting the .codeium directory in your home directory. Thanksssss!!

free-engineer commented 2 weeks ago

I was able to check the error details from the menu [help] - [Toggle Developer Tools] in VSCode.

[Extension Host] (VSCode) 2024-10-22 06:38:41 [INFO]: Using cached LS with valid crc32: /home/username/.vscode-server/extensions/codeium.codeium-1.22.5/dist/1347d6f7fffdaec404d99b3f0ca3d8854448c787/language_server_linux_x64
[Extension Host] (VSCode) 2024-10-22 06:38:41 [INFO]: Language server started
  ERR spawn /home/username/.vscode-server/extensions/codeium.codeium-1.22.5/dist/1347d6f7fffdaec404d99b3f0ca3d8854448c787/language_server_linux_x64 ENOENT: Error: spawn /home/username/.vscode-server/extensions/codeium.codeium-1.22.5/dist/1347d6f7fffdaec404d99b3f0ca3d8854448c787/language_server_linux_x64 ENOENT
    at ChildProcess._handle.onexit (node:internal/child_process:286:19)
    at onErrorNT (node:internal/child_process:484:16)
    at process.processTicksAndRejections (node:internal/process/task_queues:82:21)
[Extension Host] (VSCode) 2024-10-22 06:39:41 [ERROR]: Language server port file not found in /tmp/01e4f34d-3ebb-465a-9a90-fed086055fc4/codeium/manager after 60s

It seemed that the language_server_linux_x64 was failing to start, so I checked using:

ldd language_server_linux_x64

The result showed: "Error loading shared library libresolv.so.2: No such file or directory (needed by language_server_linux_x64)". Given this, I tried various solutions, including:

apk add gcompat

While it attempted to start, it encountered different errors and still wouldn't run.

Then I realized that my environment is Windows 11 + WSL2 + Docker container, and moreover, the container is Alpine-based. Upon checking the official website, I found out that it might not work in this setup...🥲

https://code.visualstudio.com/docs/remote/linux

Supported in Dev Containers and WSL. Extensions installed in the container may not work due to glibc dependencies in extension native code.

Abeautifulsnow commented 1 week ago

Try deleting the .codeium directory in your home directory.

It works for me, so thank u.

Joan1590 commented 1 week ago

Doesnt work with docker enviroment!

And didn't work deleting the .codenium folder

YakovL commented 4 days ago

Some suggestions can also be found on SO, including a suggestion not to delete the whole .codeium, but just language_server_v* in it. As for me, I've temporarily switched to another copilot, but hope this will get resolved consistently

jorlan259 commented 2 days ago

I get the same error when I try to run in dev-container with Alpine-based, if anyone knows how to fix it, I would be very grateful.