Closed WhyNotHugo closed 2 years ago
Does it crash non-containerized? If the answer is no, this belongs on our discourse.
Sorry, I didn't actually mention this here: my question is how to debug this further. I don't mind attempting to address this myself, but am kinda stuck trying to figure out how to debug in LSP in general.
I haven't tried in a non-containerised context; haven't gotten around to setting up a suitable environment for that.
Sorry, I didn't actually mention this here: my question is how to debug this further.
And the point is that such questions don't belong on a bug tracker, sorry. Use the Discourse link from the issue template or ask on Matrix.
(If it turns out to be a bug in lspconfig, feel free to edit the issue and reopen or ping a maintainer to do it.)
For anyone curious on this, it turned out to be related to https://github.com/microsoft/vscode-languageserver-node/issues/857. https://github.com/lspcontainers/lspcontainers.nvim/pull/49/files has further details.
Description
Volar crashes shortly after startup. I can't quite figure out why, nor have any clue on how to debug this further.
I'm running it containerised. I've logged all communication with the LSP by slipping in a special wrapper (note: I only used the wrapper for this bit; all other gathering of logs was done using the LSP normally without this wrapper):
stdin:
stdout:
stderr is empty.
Neovim version
NVIM v0.6.0-dev+529-g97ae0ab4d Build type: RelWithDebInfo LuaJIT 2.0.5 Compilation: /usr/bin/cc -march=x86-64 -mtune=generic -O2 -pipe -fno-plt -fexceptions -Wp,-D_FORTIFY_SOURCE=2 -Wformat -Werror=format-security -fstack-clash-protection -fcf-protection -Wp,-U_FORTIFY_SOURCE -Wp,-D_FORTIFY_SOURCE=1 -DNVIM_TS_HAS_SET_MATCH_LIMIT -O2 -g -Og -g -Wall -Wextra -pedantic -Wno-unused-parameter -Wstrict-prototypes -std=gnu99 -Wshadow -Wconversion -Wmissing-prototypes -Wimplicit-fallthrough -Wvla -fstack-protector-strong -fno-common -fdiagnostics-color=auto -DINCLUDE_GENERATED_DECLARATIONS -D_GNU_SOURCE -DNVIM_MSGPACK_HAS_FLOAT32 -DNVIM_UNIBI_HAS_VAR_FROM -DMIN_LOG_LEVEL=3 -I/build/neovim-git/src/build/config -I/build/neovim-git/src/neovim-git/src -I/usr/include -I/build/neovim-git/src/build/src/nvim/auto -I/build/neovim-git/src/build/include Compiled by builduser
Features: +acl +iconv +tui See ":help feature-compile"
system vimrc file: "$VIM/sysinit.vim" fall-back for $VIM: "/usr/share/nvim"
Run :checkhealth for more info
Nvim-lspconfig version
27d2c116fdea5614f422dcbcae63da01a1415fcf
Operating system and version
Linux 5.15.2-arch1-1 GNU/Linux
Affected language servers
Volar, bash-language-server
Steps to reproduce
npm init vite@latest
, picking thevue-ts
option.nvim -u minimal.lua src/App.vue
Actual behavior
LSP should not crash, or should show some clues as to what went wrong.
Expected behavior
LSP exits silently with no indicator of what's wrong.
Minimal config
Health check
LSP log
https://gist.github.com/WhyNotHugo/9347009cf52f8baf05ce0958ae6d5f7b