Closed ghost closed 1 year ago
This can happen if calling out to uname fails for some reason. I'll add logging tonight for uname output.
Oh okay. :) Don't know why uname sometimes fails here.
I have pushed a commit that adds a debug for this failing:
export DEBUG_CODEIUM=debug
nvim
You will then find the log under ~/.cache/nvim/codeium.log
I was able to replicate this issue on Windows, which of course doesn't have uname
. Is windows not currently supported?
You will then find the log under
~/.cache/nvim/codeium.log
I'm not sure, but here it seems as if it can't find the executable, nothing gets logged and most plugins gets disabled (which is what normally happens when a plugin failes for one reason or another). Maybe it would be better with and option that lets the user set the path to the executable?
Maybe it would be better with and option that lets the user set the path to the executable?
You can use the tools.language_server
option to do this.
have this error on windows, doesn't install just errors: uname: Executable not found
, I'm not sure if it's even downloading it.
Even when manually setting locations for the language_server
it doesn't work.
@A-Lamia Windows is not currently supported, as I no longer have a license to do development+testing. This will require a PR.
@jcdickinson I haven't developed a plugin (and don't know much lua) before but I am getting the same error uname: Executable not found
on windows.
the stack trace leads me to this line in plenary, that is called from this line in codeium.nvim
Is it possible to try-catch on this and assume windows if it fails?
I could, but then more things would fail. This code should never be executed if the server binary is up to date. You could try manually downloading the binary: https://github.com/Exafunction/codeium/releases/tag/language-server-v1.1.42
Then use the tools.language_server config option to point the plugin at it.
I resolved this issue in Linux by chmod +x ~/.cache/nvim/codeium/bin/1.1.42/language_server_macos_x64
.
@CroPhYPtic can you update and see if this is still an issue?
This should be fixed with the use of vim.loop.os_uname()
@CroPhYPtic can you update and see if this is still an issue?
Sorry for a very late reply. I've been doing things withoiut AI help for a while. This issue seems to be solved. :)
This should be fixed with the use of
vim.loop.os_uname()
Yep, it seems to be fixed. :)
For some reason, sometimes, the executable can't be found. It reports this error:
I'm running on Linux, so I don't know why it even bothers checking for the windows executable? Anyway, the executable is accessable in the directory so honestly don't know why it sometimes can't find it.