Open FEIFEIEIAr opened 6 months ago
Is your user directory an NFS mount?
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.
@michaelli611 maybe we should figure out a permanent solution for this
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
I'm facing the same issue. Is there a solution available?
VSCode: 1.89.1 Codeium: 1.8.45 OS: Windows 10
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
Try deleting the .codeium directory in your home directory.
Try deleting the .codeium directory in your home directory.
actually helped! Thanks
Try deleting the .codeium directory in your home directory.
Deleting the C:\Users\User\ .codeium directory resolved the issue on Windows. Thank you!
Try deleting the .codeium directory in your home directory.
Success in MacOS, Thanks.
Try deleting the .codeium directory in your home directory.
Deleting the .codeium worked for me, Thank You!!!!
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 :(.
Try deleting the .codeium directory in your home directory.
Works for me too. Thanks!
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.
Deleting the .codeium directory did not work for me as well.
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?
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.)
Have the same problem on termux code-oss build
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.
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).
Try deleting the .codeium directory in your home directory.
This solution worked for me, Im using VSCode on Windows 10
I am also facing the same issue
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.
Try deleting the .codeium directory in your home directory.
This works for me
Success in MacOS, Thanks.
Deleting the .codeium folder from path (C:\Users\Laptop Home[may vary on your system]) worked 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
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 :)
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.
Deleting .codeium doesnt work for me on windows 10
Try deleting the .codeium directory in your home directory. Thanksssss!!
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.
Try deleting the .codeium directory in your home directory.
It works for me, so thank u.
Doesnt work with docker enviroment!
And didn't work deleting the .codenium folder
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
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.
I encountered with following problem when using codeium on VSCode and Ubuntu.
And the log says,
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.