Skip to content

VS code extension fails on Windows 11 #1

Description

@ulysses4ever

I've been trying to run SaSYLF on Windows with the VScode extension and I keep running into the following error which causes the language server to crash repeatedly and then not be restarted.

Node.js v22.17.0
[Info  - 10:09:37 PM] Connection to server got closed. Server will restart.
node:fs:562
  return binding.open(
                 ^
 
Error: ENOENT: no such file or directory, open 'c:\Users\username\.vscode\extensions\sasylf.sasylf-2.0.0\logs\2025-09-09T03:09:37.667Z.log'
    at Object.openSync (node:fs:562:18)
    at Object.func [as openSync] (node:electron/js2c/node_init:2:2617)
    at Object.writeFileSync (node:fs:2453:35)
    at createLogFile (c:\Users\username\.vscode\extensions\sasylf.sasylf-2.0.0\server\out\utils.js:153:12)
    at logErrorToFile (c:\Users\username\.vscode\extensions\sasylf.sasylf-2.0.0\server\out\utils.js:160:25)
    at validateTextDocument (c:\Users\username\.vscode\extensions\sasylf.sasylf-2.0.0\server\out\server.js:142:36) {
  errno: -4058,
  code: 'ENOENT',
  syscall: 'open',
  path: 'c:\\Users\\username\\.vscode\\extensions\\sasylf.sasylf-2.0.0\\logs\\2025-09-09T03:09:37.667Z.log'
}
 
Node.js v22.17.0
[Error - 10:09:37 PM] Connection to server got closed. Server will not be restarted.
[Error - 10:09:37 PM] Request textDocument/documentSymbol failed.
Error: Connection got disposed.
    at Object.dispose (c:\Users\username\.vscode\extensions\sasylf.sasylf-2.0.0\client\node_modules\vscode-jsonrpc\lib\common\connection.js:1044:27)
    at Object.dispose (c:\Users\username\.vscode\extensions\sasylf.sasylf-2.0.0\client\node_modules\vscode-languageclient\lib\common\client.js:73:35)
    at LanguageClient.handleConnectionClosed (c:\Users\username\.vscode\extensions\sasylf.sasylf-2.0.0\client\node_modules\vscode-languageclient\lib\common\client.js:2424:42)
    at LanguageClient.handleConnectionClosed (c:\Users\username\.vscode\extensions\sasylf.sasylf-2.0.0\client\node_modules\vscode-languageclient\lib\node\main.js:155:15)
    at closeHandler (c:\Users\username\.vscode\extensions\sasylf.sasylf-2.0.0\client\node_modules\vscode-languageclient\lib\common\client.js:2411:18)
    at CallbackList.invoke (c:\Users\username\.vscode\extensions\sasylf.sasylf-2.0.0\client\node_modules\vscode-jsonrpc\lib\common\events.js:55:39)
    at Emitter.fire (c:\Users\username\.vscode\extensions\sasylf.sasylf-2.0.0\client\node_modules\vscode-jsonrpc\lib\common\events.js:117:36)
    at closeHandler (c:\Users\username\.vscode\extensions\sasylf.sasylf-2.0.0\client\node_modules\vscode-jsonrpc\lib\common\connection.js:256:26)
    at CallbackList.invoke (c:\Users\username\.vscode\extensions\sasylf.sasylf-2.0.0\client\node_modules\vscode-jsonrpc\lib\common\events.js:55:39)
    at Emitter.fire (c:\Users\username\.vscode\extensions\sasylf.sasylf-2.0.0\client\node_modules\vscode-jsonrpc\lib\common\events.js:117:36)
    at IPCMessageReader.fireClose (c:\Users\username\.vscode\extensions\sasylf.sasylf-2.0.0\client\node_modules\vscode-jsonrpc\lib\common\messageReader.js:40:27)
    at ChildProcess.<anonymous> (c:\Users\username\.vscode\extensions\sasylf.sasylf-2.0.0\client\node_modules\vscode-jsonrpc\lib\node\main.js:33:45)
    at ChildProcess.emit (node:events:530:35)
    at maybeClose (node:internal/child_process:1101:16)
    at Process.ChildProcess._handle.onexit (node:internal/child_process:304:5)

Here's the information on the version of VS code and Windows I'm running

Windows

Edition     Windows 11 Pro
Version     23H2
Installed on      ‎8/‎27/‎2025
OS build    22631.5768
Experience  Windows Feature Experience Pack 1000.22700.1106.0

VS code

Version: 1.103.2 (user setup)
Commit: 6f17636121051a53c88d3e605c491d22af2ba755
Date: 2025-08-20T16:45:34.255Z
Electron: 37.2.3
ElectronBuildId: 12035395
Chromium: 138.0.7204.100
Node.js: 22.17.0
V8: 13.8.500258-electron.0
OS: Windows_NT x64 10.0.22631

I've tried reinstalling the extension, reinstalling VScode, and I've confirmed that the c:\Users\username.vscode\extensions\sasylf.sasylf-2.0.0\logs folder exists. I've also tested this on another computer running Windows 11 and ran into the same issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

No labels
No labels

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions