You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
## versions
vim version: VIM - Vi IMproved 9.0 9001499
node version: v16.15.1
coc.nvim version: 0.0.82-baac60ac 2025-01-13 11:27:36 +0800
coc.nvim directory: /home/sylvain/.vim/plugged/coc.nvim
term: tmux
platform: linux
## Log of coc.nvim
2025-02-01T19:40:49.148 DEBUG (pid:38791) [core-documents] - buffer created 1 true file:///home/sylvain/Projects/wallet-valuator/src/services/cryptoresolvers/compositecryptoresolver.mts
2025-02-01T19:40:49.151 DEBUG (pid:38791) [core-editors] - editor created winid & bufnr & tabpageid: 1000 1 1
2025-02-01T19:40:49.215 INFO (pid:38791) [plugin] - coc.nvim initialized with node: v16.15.1 after 188
2025-02-01T19:40:49.263 INFO (pid:38791) [services] - service tsserver started
2025-02-01T19:44:59.026 INFO (pid:38791) [attach] - Request action: codeAction []
2025-02-01T19:45:02.027 ERROR (pid:38791) [timing] - Request timeout after 3000ms
2025-02-01T19:50:12.806 DEBUG (pid:38791) [core-documents] - document detach 1 file:///home/sylvain/Projects/wallet-valuator/src/services/cryptoresolvers/compositecryptoresolver.mts
Describe the bug
I don't know if this is a bug or if the software was designed that way. Nevertheless, I noticed when I call CocAction('codeAction') to apply a change, the changes menu does appear, but Vim hangs for 60s. After that, I have a "timeout" error message (see screenshots below). Vim is then responsive, and I can choose and apply the code action as expected.
Interestingly, if I call CocActionAsync('codeAction'), it works as expected without a noticeable delay in the Vim reactiveness.
Can you explain that behavior? Is it a bug or not? Are there any drawbacks in using CocActionAsync vs CocAction?
Thank you for your time and the great work on CoC.nvim. It is an amazing project for Vim lovers like me!
Reproduce the bug
I see that behavior both when using my everyday vimrc as well as when using the mini.vim below:
I am running a fresh installation of Debian Bookworm.
Vim is the version shipped with Debian
CoC was installed from the release version using Plug.
I am using CoC on a TypeScript project (small to moderate size)
Tsserver was installed from Vim, as explained in the README
node is v6.15.1 (version shipped by Debian)
Screenshots
1
Open a TypeScript file using Vim, placing the cursor on a keyword with some code action available.
On the bottom half of the screen, you see the logs. Nothing noticeable for me.
Type :call CocAction('codeAction')
2
Press enter.
The selection menu does appear, but Vim is no longer responsive.
3
After 60 seconds, I see an error message. Vim is responsive again.
The text was updated successfully, but these errors were encountered:
Result from CocInfo
Describe the bug
I don't know if this is a bug or if the software was designed that way. Nevertheless, I noticed when I call
CocAction('codeAction')
to apply a change, the changes menu does appear, but Vim hangs for 60s. After that, I have a "timeout" error message (see screenshots below). Vim is then responsive, and I can choose and apply the code action as expected.Interestingly, if I call
CocActionAsync('codeAction')
, it works as expected without a noticeable delay in the Vim reactiveness.Can you explain that behavior? Is it a bug or not? Are there any drawbacks in using
CocActionAsync
vsCocAction
?Thank you for your time and the great work on
CoC.nvim
. It is an amazing project for Vim lovers like me!Reproduce the bug
I see that behavior both when using my everyday
vimrc
as well as when using themini.vim
below:Plug
.Screenshots
1
Open a TypeScript file using Vim, placing the cursor on a keyword with some code action available.
On the bottom half of the screen, you see the logs. Nothing noticeable for me.
Type
:call CocAction('codeAction')
2
Press enter.
The selection menu does appear, but Vim is no longer responsive.
3
After 60 seconds, I see an error message. Vim is responsive again.
The text was updated successfully, but these errors were encountered: