VSCodeVim / VSCodeVim/Vim

Failed to handle key=. Failed to attach to neovim process. Timeout

Open
#7,148 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

kind/bug
Dominant language
TypeScript
Stars
15.2k
Forks
1.5k
Avg merge
3d 18h
Merged PRs (30d)
6

Description

To Reproduce
Steps to reproduce the behavior:

  1. Go to '...'
  2. Click on '....'
  3. Scroll down to '....'
  4. See error

VSCodeVim version: 1.21.8

Stack trace
Error: Failed to handle key=
. Failed to attach to neovim process. Timeout
    at p.statusBarText [as run] (/home/chen/.vscode/extensions/vscodevim.vim-1.21.8/src/neovim/neovim.ts:46:15)
    at Object.vimState [as Run] (/home/chen/.vscode/extensions/vscodevim.vim-1.21.8/src/cmd_line/commandLine.ts:79:19)
    at C.j [as exec] (/home/chen/.vscode/extensions/vscodevim.vim-1.21.8/src/actions/commands/commandLine.ts:144:50)
    at C.execCount (/home/chen/.vscode/extensions/vscodevim.vim-1.21.8/src/actions/base.ts:230:42)
    at I.actionToRecord [as runAction] (/home/chen/.vscode/extensions/vscodevim.vim-1.21.8/src/mode/modeHandler.ts:713:47)
    at I.handledAsAction [as handleKeyAsAnAction] (/home/chen/.vscode/extensions/vscodevim.vim-1.21.8/src/mode/modeHandler.ts:662:43)
    at I.text [as handleKeyEvent] (/home/chen/.vscode/extensions/vscodevim.vim-1.21.8/src/mode/modeHandler.ts:477:11)
    at /home/chen/.vscode/extensions/vscodevim.vim-1.21.8/extensionBase.ts:370:73

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the stack-trace entry point at src/neovim/neovim.ts:46, then follow the command-line path through src/cmd_line/commandLine.ts and src/actions/commands/commandLine.ts. Reproduce the VSCodeVim 1.21.8 timeout and trace the Neovim attachment flow; done means the reported key no longer fails with a timeout.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript, vim, vscode
Domain
devtools
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.