New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
No suggestions when using 1.6.39 #354
Comments
Can you try the latest commit? |
@pqn makes no difference. Trying 1.6.36 didn't work either. How can I debug this? |
The code to do the extraction hasn't changed in recent memory. You could try manually unzipping it to see if it can skip that step. |
The plot thickens. It's not a zip file, it's an HTML file with a 404 |
Pretty sure the problem is due to changes in commit fd440cd Looks like the code for extracting the archive isn't catching errors from else
if !executable('gzip')
call codeium#log#Error('Failed to extract language server binary: missing `gzip`.')
return ''
endif
call system('gzip -d ' . s:bin . '.gz')
call system('chmod +x ' . s:bin)
endif
if !filereadable(s:bin)
call codeium#log#Error('Failed to download language server binary.')
return ''
endif Looks like I was able to solve this for myself by manually constructing the url and downloading it from the github url Side note, there also appears to exists another version which matches the tagged version of my plugin which I was instructed to install, but it appears the newer one is working ok 👌 |
FYI @fortenforge |
Tried another codeium instance, version 1.6.39 and I'm not getting any suggestions.
I'm using version 1.6.28 (on another codeium instance) and it's working fine.
Hard to provide much in the way of useful debugging information, for example, not sure which version the language server on my system is running.
Digging around, the language server integration looks like a possible culprit.
for one it doesn't look like the language server is extracted.
Also, the commit of tag
1.6.39
5b8f68d is the same as1.8.5
and I'm not sure if the language server version 1.8.5 is supposed to work with 1.6.39 or notThe text was updated successfully, but these errors were encountered: