elm-language-server: Erratic/broken behavior with Neovim's integrated LSP client (2)
It’s the same issue as #503
I had this issue before and solved with the suggested solution
if client.config.flags then
client.config.flags.allow_incremental_sync = true
end
but now it’s happening again:

Neovim version:
NVIM v0.5.0-dev+1318-g61aefaf29
Build type: RelWithDebInfo
LuaJIT 2.1.0-beta3
Compilation: /usr/bin/cc -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1 -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=always -DINCLUDE_GENERATED_DECLARATIONS -D_GNU_SOURCE -DNVIM_MSGPACK_HAS_FLOAT32 -DNVIM_UNIBI_HAS_VAR_FROM -DMIN_LOG_LEVEL=3 -I/home/runner/work/neovim/neovim/build/config -I/home/runner/work/neovim/neovim/src -I/home/runner/work/neovim/neovim/.deps/usr/include -I/usr/include -I/home/runner/work/neovim/neovim/build/src/nvim/auto -I/home/runner/work/neovim/neovim/build/include
Compilado por runner@fv-az139-369
Features: +acl +iconv +tui
About this issue
- Original URL
- State: closed
- Created 3 years ago
- Reactions: 2
- Comments: 41 (14 by maintainers)
@Razzeee Update: Another Neovim LSP client called CoC is showing the same error:
I just grabbed a copy of v2.2.0. After a few minutes, I don’t see this happening. I can assume it’s fixed since I was on v2.1.0.
@Razzeee Reverting elm-language-server to 2.0.3 fixes the problem. Something on the 2.1.0 is broken