VSCodeVim / VSCodeVim/Vim

uncaught exception in sharedProcess

Open
#8,929 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

2024-03-08 02:54:22.931 [error] [uncaught exception in sharedProcess]: Error: ENOENT: no such file or directory, stat 'c:\Users\artist.vscode-insiders\extensions\extensions.json.vsctmp': EntryNotFound (FileSystemError): Error: ENOENT: no such file or directory, stat 'c:\Users\artist.vscode-insiders\extensions\extensions.json.vsctmp'
at r.create (c:\dev\VSCode-win32-x64-1.88.0-insider\resources\app\out\vs\code\node\sharedProcess\sharedProcessMain.js:51:30092)
at a (c:\dev\VSCode-win32-x64-1.88.0-insider\resources\app\out\vs\code\node\sharedProcess\sharedProcessMain.js:51:30207)
at i.fb (c:\dev\VSCode-win32-x64-1.88.0-insider\resources\app\out\vs\code\node\sharedProcess\sharedProcessMain.js:56:36633)
at i.stat (c:\dev\VSCode-win32-x64-1.88.0-insider\resources\app\out\vs\code\node\sharedProcess\sharedProcessMain.js:56:29079)
at async v.stat (c:\dev\VSCode-win32-x64-1.88.0-insider\resources\app\out\vs\code\node\sharedProcess\sharedProcessMain.js:56:16225)
at async K.sb (c:\dev\VSCode-win32-x64-1.88.0-insider\resources\app\out\vs\code\node\sharedProcess\sharedProcessMain.js:102:108261)
版本: 1.88.0-insider
提交: ea142b5ccdcb797b1de6b1a46fecbf25dea2e229
日期: 2024-03-06T05:47:45.312Z
Electron: 28.2.5
ElectronBuildId: 27336930
Chromium: 120.0.6099.291
Node.js: 18.18.2
V8: 12.0.267.19-electron.0
OS: Windows_NT x64 10.0.19045

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

The report only includes a compiled VS Code sharedProcess stack from VS Code Insiders 1.88.0 on Windows; no repository file, reproduction steps, or failing test is identified. Start by determining whether the error can be reproduced with the VSCodeVim extension enabled, then locate the related source entry point. Done means identifying the cause and preventing this uncaught exception.

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.