-
Notifications
You must be signed in to change notification settings - Fork 124
error starting LSP client: nil #428
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
Comments
This actually appears to be related to auth method. An auth token generated by |
Thank you for figuring out the root cause! |
In the current version, it seems that using |
I can confirm that if the env bars are not set and I use copilot with things work fine. |
I'll investigate if this works now with copilot auth and the env bars set (it didn't before) |
If I have |
So I still cannot replicate the nil error, however throughout my tests (and asking tpope maintainer of copilot.vim) that the token generated by the |
nvim 0.11 same issue |
Are you also on OSX? |
yes osx, |
if set ~/software/nvim/lazy/plugins/copilot.lua/copilot/darwin-arm64 I've change the plugins directory from Does this cause the problem? |
Hmm, not sure. |
Download from https://github.com/github/copilot-language-server-release/releases/tag/1.298.0 |
What happens if you run it directly from the command line? |
If I run the language server it just waits and I have to ctrl-C, that happens with or without the env var set. Same on node and binary. I can successfully use the permanent login method, following the steps for the env based approach however, results in the same thing - no idea why, but for now, I'll just use the permanent method. |
This one bugs me as I have no idea why it behaves this way in your environment :( |
I wonder if it's because I have GH_TOKEN set also (for other purposes) |
same |
seems worked now, I'm not sure what changes |
FWIW, I was getting this as a race condition on about half of Nvim starts. Adding Specifically this error: |
I had |
Between the
beta
branch andmaster
there appears to be some sort of issue.I'm on Neovim 0.11 and I get error on startup "error starting LSP client: nil". On
beta
I do not.What's odd is that the lsp client appears to have started and LSPInfo shows it. I've tried
binary
andnodejs
for the server type - same either way.This doesn't seem to happen on 0.10.5 - same configs, but in fairness that's a debian install and i'm on osx usually.
I don' think this has to do with downloading the binary - it seems to do that fine and I can run the downloaded js or binary fine.
I've enabled logging and when it fails it looks like this:
The text was updated successfully, but these errors were encountered: