Failed to handle key `<C-v>`: Cannot read properties of null (reading 'pushUndoStop')
Open
Nobody has claimed this yet.
- 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:
- Go to '...'
- Click on '....'
- Scroll down to '....'
- See error
VSCodeVim version: 1.24.3
Stack trace
TypeError: Cannot read properties of null (reading 'pushUndoStop')
at i.applyEdits (vscode-file://vscode-app/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:1565:13541)
at uc.$tryApplyEdits (vscode-file://vscode-app/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:2299:13948)
at m.N (vscode-file://vscode-app/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:1573:15220)
at m.M (vscode-file://vscode-app/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:1573:14938)
at m.H (vscode-file://vscode-app/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:1573:14031)
at m.G (vscode-file://vscode-app/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:1573:13012)
at vscode-file://vscode-app/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:1573:11800
at g.invoke (vscode-file://vscode-app/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:86:145)
at n.deliver (vscode-file://vscode-app/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:86:2029)
at a.fire (vscode-file://vscode-app/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:86:1667)
at r.fire (vscode-file://vscode-app/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:553:15219)
at Z.onmessage (vscode-file://vscode-app/Applications/Visual Studio Code.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:1671:1490)
Additional context
currentMode: "Insert"
cursors: [
"[[0, 0] | [0, 0]]"
]
actionsRunPressedKeys: [
"c",
"<BS>",
"<right>",
"<BS>",
"a",
"<BS>",
"<C-v>"
]
actionsRun: [
"K",
"B",
"I"
]
textTransformations: [
{
"type": "insertText",
"position": {
"line": 0,
"character": 0
},
"text": "Now, let's add some variables that are important for the algorithm.\n\n- linkage: The linkage method is applied to the link community algorithm.\n\n- nlog10: Take the logarithm of the data in case it is very heterogeneous.\n\n- lookup: For computing similarities and in the case of nlog10=T, set the zeros into the maximum value of the transformation.\n\n- mapping: Variable used together with nlog10, lookup, and prob. There are three mappings or transformations for the data: **R1** (invert the order), **R2** (preserve the order), and **trivial** (no transformation).\n\n- prob: If the data are probabilities, check that values are in the range (0, 1).\n\n- cut: Compute the quality functions in the link community process using all the steps (**False**) or only the steps which different link community dendrogram heights (**True**).\n\n- mode: Old feature. Associated to the self-loop weight in the feature vectors. Currently, the **ALPHA** mode, the average of the feature vector, and the **BETA** mode, the average using the opposite direction, are supported. The **ALPHA** mode is the traditional one.\n\n- topology: There are three topologies: **SOURCE**, **TARGET**, and **MIX**. This variable determines the direction of the similarities between the nodes\n\n- opt_score: Quality functions to find the best partition. Currently, there are three: $D$ (average link density), **$\\chi$** (susceptibility), and the maximum **$\\mu$**-score.\n",
"cursorIndex": 0
}
]
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the reported Ctrl-v failure in VSCodeVim 1.24.3 using the listed key sequence and inspect the provided stack trace, which points into VS Code's applyEdits path. No repository file or test is named, so locate the command handling this sequence before determining how to verify that the null pushUndoStop error no longer occurs.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript, vscode
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100