vls: Client has shut down after sending a message

neovim / nvim-lspconfig

Quickstart configs for Nvim LSP

Apache License 2.0

10.46k stars 2.06k forks source link

vls: Client has shut down after sending a message #266

Closed kkharji closed 4 years ago

kkharji commented 4 years ago

nvim --version: nightly
nvim-lsp version(commit hash): current

:checkhealth result


## Checking language server protocol configuration
- INFO: html: configuration checked.
- INFO: bashls: configuration checked.
- INFO: cssls: configuration checked.
- INFO: jsonls: configuration checked.
- INFO: tsserver: configuration checked.
- INFO: vimls: configuration checked.
- INFO: intelephense: configuration checked.
- INFO: vuels: configuration checked.



- What language server(If the problem is related to a specific language server): Vue Language Server
- Operating system/version: Linux
- Terminal name/version:
- `$TERM`:

### How to reproduce the problem from neovim startup
- LspInstall vuels
- add `call luaeval("require'nvim_lsp'.vuels.setup{}")`
- open vue file

### Actual behaviour

### Expected behaviour
Vue Language server working fine

h-michael commented 4 years ago

@tamibam Could you show me sample codes or project?

lithammer commented 4 years ago

I'm also seeing this for bashls and pyls_ms. The thing is, the language server actually starts and works just fine.

Could you show me sample codes or project?

I can reproduce with just an empty .sh or .py file.

kkharji commented 4 years ago

@h-michael Hay, michael, any empty vue file will call the server and this message appere

h-michael commented 4 years ago

I see, I'll invest this.

justinmk commented 4 years ago

Thanks for your report. The configs here are best-effort:

It is hoped that these configurations serve as a "source of truth", but they are strictly best effort. If something doesn't work, these configs are useful as a starting point, which you can adjust to fit your environment.

If you have an improvement or fix, please send a PR!
If you have a specific question we'll try to answer it (keeping in mind the configs in this repo are best-effort and unsupported).
If you found a bug in the core lsp module, the best way to get it fixed is to describe steps to reproduce it without the particular LSP server and other factors particular to your environment. Or better, by adding a failing test case to lsp_spec.lua, which has code to setup a fake LSP server to simulate various scenarios.