Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
lsp server doesn't start using coc.vim
See original GitHub issueI’m having the same issue described here:
https://github.com/neoclide/coc.nvim/issues/3687
and here:
https://stackoverflow.com/questions/68750196/graphql-lsp-with-coc-neovim
I gather these logs:
vim version: NVIM v0.7.0-dev+1233-gabbc9148d
node version: v17.5.0
coc.nvim version: 0.0.80-a554a31c 2022-03-11 19:04:48 +0800
coc.nvim directory: $HOME/.vim/bundle/coc.nvim
term: tmux
platform: linux
## Log of coc.nvim
2022-03-11T09:17:35.905 INFO (pid:3255126) [services] - registered service "languageserver.graphql"
2022-03-11T09:17:35.908 INFO (pid:3255126) [services] - graphql state change: stopped => starting
2022-03-11T09:17:35.935 INFO (pid:3255126) [plugin] - coc.nvim initialized with node: v17.5.0 after 87ms
2022-03-11T09:17:35.940 INFO (pid:3255126) [language-client-index] - Language server "languageserver.graphql" started with 3255169
2022-03-11T09:17:36.264 INFO (pid:3255126) [services] - graphql state change: starting => running
2022-03-11T09:17:36.268 INFO (pid:3255126) [services] - service languageserver.graphql started
2022-03-11T09:17:36.312 INFO (pid:3255126) [services] - graphql state change: running => stopped
2022-03-11T09:17:36.312 INFO (pid:3255126) [services] - graphql state change: stopped => starting
2022-03-11T09:17:36.315 INFO (pid:3255126) [language-client-index] - Language server "languageserver.graphql" started with 3255218
2022-03-11T09:17:36.633 INFO (pid:3255126) [services] - graphql state change: starting => running
2022-03-11T09:17:36.678 INFO (pid:3255126) [services] - graphql state change: running => stopped
2022-03-11T09:17:36.678 INFO (pid:3255126) [services] - graphql state change: stopped => starting
2022-03-11T09:17:36.680 INFO (pid:3255126) [language-client-index] - Language server "languageserver.graphql" started with 3255249
2022-03-11T09:17:36.991 INFO (pid:3255126) [services] - graphql state change: starting => running
2022-03-11T09:17:37.034 INFO (pid:3255126) [services] - graphql state change: running => stopped
2022-03-11T09:17:37.034 INFO (pid:3255126) [services] - graphql state change: stopped => starting
2022-03-11T09:17:37.037 INFO (pid:3255126) [language-client-index] - Language server "languageserver.graphql" started with 3255260
2022-03-11T09:17:37.342 INFO (pid:3255126) [services] - graphql state change: starting => running
2022-03-11T09:17:37.386 INFO (pid:3255126) [services] - graphql state change: running => stopped
2022-03-11T09:17:40.344 INFO (pid:3255126) [attach] - receive notification: showInfo []
Issue Analytics
- State:
- Created 2 years ago
- Reactions:7
- Comments:65 (33 by maintainers)
Top Results From Across the Web
Not getting LSP completion for neovim lua commands #2516
I have setup coc completion for lua language from here and I'm getting completion for almost everything except for neovim built in commands ......
Read more >Anybody else feel built in LSP still lacking behind CoC?
I'd love to use neovim's built in LSP because it's lightweight. I spent about two hours today fiddling with it, and couldn't get...
Read more >In my experience, the built in LSP is a mixed bag. Getting ...
In my experience, the built in LSP is a mixed bag. Getting language servers configured is a breeze, diagnostics and go-to definition work...
Read more >User Manual - rust-analyzer
This manual focuses on a specific usage of the library — running it as part of a server that implements the Language Server...
Read more >neoclide/coc.nvim - Gitter
I did that, but it broke during communication with vim/coc.nvim. so I wanted to know ... showOutput 's LSP server, as this output...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
@benjie thank you! Hopefully someone has time or interest. @stonexer perhaps you‘d be interested in taking a look? Both vscode and nvim coc have changed their exception handling all of a sudden and I just resolved the former.
I think it’s just a lingering uncaught exception somewhere, or just that the LSP server is behaving differently because of something the nvim coc client expects. I tried debugging the LSP server with vim to log to output channel uncaught exceptions using
process.on(), but i couldn’t get my vim instance to load the locally built LSP server I was trying to debug, or this was not showing an uncaught exception. I at least figured out some of the COC commands for debugging the lsp server in vim.@wongjiahau glad to hear it’s not just me and that there are workarounds for both CoC and the native LSP client.