Open FEIFEIEIAr opened 2 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.
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 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.