LspStop requiring an argument in neovim v0.11.2

[harriott]

Description

Up until neovim v0.11.1, :LspStop worked fine without arguments.
Since upgrading to neovim v0.11.2, on Arch Linux and Windows 10 Pro,

:LspStop
E5108: Error executing lua: vim/_editor.lua:0: nvim_exec2(), line 1: Vim:E471: Argument required: LspStop
stack traceback:
        [C]: in function 'nvim_exec2'
        vim/_editor.lua: in function 'cmd'
        .../nvim/lazy/telescope.nvim/lua/telescope/actions/init.lua:381: in function 'run_replace_or_original'
        ...re/nvim/lazy/telescope.nvim/lua/telescope/actions/mt.lua:65: in function 'run_replace_or_original'
        ...re/nvim/lazy/telescope.nvim/lua/telescope/actions/mt.lua:65: in function 'key_func'
        ...hare/nvim/lazy/telescope.nvim/lua/telescope/mappings.lua:253: in function <...hare/nvim/lazy/telescope.nvim/lua/telescope/mappings.lua:252>
Press ENTER or type command to continue

and following that,

:LspStop
E471: Argument required

What to do? :LspStop, a previously simple command has now become a complex riddle - for example how to use get_clients function to get the "client_id" (see :h LspStop)? (And what even is the "config_name"?)

[justinmk]

did you try :LspStop <tab>? it should autocomplete relevant config names.

meanwhile, your request should have already been addressed by #3890 . what version (exact commit) of nvim-lspconfig are you using ?

[harriott]

My apologies, I should've tried harder before posting:

1. I realised I could :LspStop ltex as a workaround.
2. :Lazy update nvim-lspconfig got me "updated from 4bc481b to f6d31b1". After that :LspStop works without arguments, as intended.