Connection refused to GLSP node server on Windows

[gee4vee]

Our extension starts up the node server like so using QuickStart components and it works fine on macOS.

  const serverProcess = new GlspServerLauncher({
    executable: path.join(__dirname, '../../server/out/graphical/index.js'),
    socketConnectionOptions: {
      port: JSON.parse(process.env.GRAPH_EDITOR_SERVER_PORT || DEFAULT_SERVER_PORT)
    },
    additionalArgs: [
      '--fileLog',
      '--logDir',
      path.join(os.homedir(), '.se-graphical')],
    logging: true,
    serverType: 'node'
  });
  context.subscriptions.push(serverProcess);
  await serverProcess.start();

Our versions are all 1.0.0 and we are running Node 16.

    "@eclipse-glsp/client": "^1.0.0",
    "@eclipse-glsp/layout-elk": "^1.0.0",
    "@eclipse-glsp/server-node": "^1.0.0",
    "@eclipse-glsp/vscode-integration": "^1.0.0",
    "@eclipse-glsp/vscode-integration-webview": "^1.0.0",
    "inversify": "^5.0.1",
    "sprotty": "^0.12.0",

However on Windows the server starts but can't connect to it. I turned off Windows Firewall but no difference. Is there anything else that could be causing this? Strangely enough, this only happens when we launch our extension in the extension host for debugging. If we package the extension into a vsix and install it, the connection to the server does happen but the diagram fails to render anyway (we can only see our tool palette and center/fit to screen buttons). And yet the GLSP server is started as a spawned node process exactly the same in both cases.

GLSP-Server: 2:26:08 PM info -  [SocketServerLauncher] The GLSP server is ready to accept new client requests on port: 5007 

extensionHostProcess.js:100
GLSP-Server: [GLSP-Server]:Startup completed

extensionHostProcess.js:100
[JsonrpcGLSPClient] Connection to server is erroring. Shutting down server. (1) [Error: connect ECONNREFUSED 127.0.0.1:5007
	at TCPConnectWrap.afterConnect [as oncomplete] (node:ne…]
extensionHostProcess.js:100
arg1:
(1) [Error: connect ECONNREFUSED 127.0.0.1:5007\n\tat TCPConnectWrap.afterConnect [as oncomplete] (node:ne…]
f @ c:\Users\gvalenc\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:100:6
e @ c:\Users\gvalenc\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:96:138916
<anonymous> @ c:\Users\gvalenc\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:96:138784
error @ c:\Users\gvalenc\git\arf\solution-editor-vscode-extension\node_modules\@eclipse-glsp\protocol\lib\jsonrpc\glsp-jsonrpc-client.js:43:17
handleConnectionError @ c:\Users\gvalenc\git\arf\solution-editor-vscode-extension\node_modules\@eclipse-glsp\protocol\lib\jsonrpc\base-jsonrpc-glsp-client.js:93:49
<anonymous> @ c:\Users\gvalenc\git\arf\solution-editor-vscode-extension\node_modules\@eclipse-glsp\protocol\lib\jsonrpc\base-jsonrpc-glsp-client.js:88:41
invoke @ c:\Users\gvalenc\git\arf\solution-editor-vscode-extension\node_modules\vscode-jsonrpc\lib\events.js:62:39
fire @ c:\Users\gvalenc\git\arf\solution-editor-vscode-extension\node_modules\vscode-jsonrpc\lib\events.js:120:36
writeErrorHandler @ c:\Users\gvalenc\git\arf\solution-editor-vscode-extension\node_modules\vscode-jsonrpc\lib\main.js:235:22
invoke @ c:\Users\gvalenc\git\arf\solution-editor-vscode-extension\node_modules\vscode-jsonrpc\lib\events.js:62:39
fire @ c:\Users\gvalenc\git\arf\solution-editor-vscode-extension\node_modules\vscode-jsonrpc\lib\events.js:120:36
fireError @ c:\Users\gvalenc\git\arf\solution-editor-vscode-extension\node_modules\vscode-jsonrpc\lib\messageWriter.js:33:27
<anonymous> @ c:\Users\gvalenc\git\arf\solution-editor-vscode-extension\node_modules\vscode-jsonrpc\lib\messageWriter.js:135:49
emit @ events:538:35
emitErrorNT @ internal/streams/destroy:157:8
emitErrorCloseNT @ internal/streams/destroy:122:3
processTicksAndRejections @ internal/process/task_queues:83:21
◀ TickObject ▶
init @ internal/inspector_async_hook:25:19
emitInitNative @ internal/async_hooks:201:43
emitInitScript @ internal/async_hooks:506:3
nextTick @ internal/process/task_queues:133:5
<anonymous> @ electron/js2c/utility_init:13:392
onDestroy @ internal/streams/destroy:96:15
Socket._destroy @ net:692:5
_destroy @ internal/streams/destroy:102:25
destroy @ internal/streams/destroy:64:5
afterConnect @ net:1166:10
callbackTrampoline @ internal/async_hooks:130:17
◀ TCPCONNECTWRAP ▶
init @ internal/inspector_async_hook:25:19
emitInitNative @ internal/async_hooks:201:43
internalConnect @ net:912:26
defaultTriggerAsyncIdScope @ internal/async_hooks:465:18
emitLookup @ net:1075:9
onlookup @ dns:73:8
callbackTrampoline @ internal/async_hooks:130:17
◀ GETADDRINFOREQWRAP ▶
init @ internal/inspector_async_hook:25:19
emitInitNative @ internal/async_hooks:201:43
lookup @ dns:157:21
<anonymous> @ net:1052:5
defaultTriggerAsyncIdScope @ internal/async_hooks:465:18
lookupAndConnect @ net:1051:3
Socket.connect @ net:989:5
start @ c:\Users\gvalenc\git\arf\solution-editor-vscode-extension\node_modules\@eclipse-glsp\vscode-integration\lib\quickstart-components\socket-glsp-vscode-server.js:64:21
activate @ c:\Users\gvalenc\git\arf\solution-editor-vscode-extension\client\src\extension.ts:408:17
processTicksAndRejections @ internal/process/task_queues:96:5
◀ await ▶
processTicksAndRejections @ internal/process/task_queues:96:5
◀ await ▶
processTicksAndRejections @ internal/process/task_queues:96:5
◀ await ▶
db @ c:\Users\gvalenc\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:108:14833
cb @ c:\Users\gvalenc\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:108:14532
<anonymous> @ c:\Users\gvalenc\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:108:12550
◀ Promise.then ▶
ab @ c:\Users\gvalenc\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:108:12470
Y @ c:\Users\gvalenc\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:108:11583
◀ await ▶
actualActivateExtension @ c:\Users\gvalenc\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:108:8591
n @ c:\Users\gvalenc\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:94:6831
m @ c:\Users\gvalenc\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:94:6792
◀ await ▶
l @ c:\Users\gvalenc\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:94:6249
f @ c:\Users\gvalenc\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:94:6176
k @ c:\Users\gvalenc\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:94:5656
j @ c:\Users\gvalenc\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:94:5611
<anonymous> @ c:\Users\gvalenc\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:94:4445
h @ c:\Users\gvalenc\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:94:4433
activateByEvent @ c:\Users\gvalenc\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:94:4110
R @ c:\Users\gvalenc\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:108:10026
<anonymous> @ c:\Users\gvalenc\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:108:20550
processTicksAndRejections @ internal/process/task_queues:96:5
◀ Promise.then ▶
$activateByEvent @ c:\Users\gvalenc\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:108:20536
N @ c:\Users\gvalenc\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:106:11223
M @ c:\Users\gvalenc\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:106:10941
H @ c:\Users\gvalenc\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:106:10034
G @ c:\Users\gvalenc\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:106:9015
<anonymous> @ c:\Users\gvalenc\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:106:7803
invoke @ c:\Users\gvalenc\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:63:145
deliver @ c:\Users\gvalenc\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:63:2066
fire @ c:\Users\gvalenc\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:63:1704
fire @ c:\Users\gvalenc\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:72:14907
<anonymous> @ c:\Users\gvalenc\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:122:16556
invoke @ c:\Users\gvalenc\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:63:145
deliver @ c:\Users\gvalenc\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:63:2066
fire @ c:\Users\gvalenc\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:63:1704
fire @ c:\Users\gvalenc\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:72:14907
<anonymous> @ c:\Users\gvalenc\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:122:14682
emit @ events:526:28
MessagePortMain._internalPort.emit @ electron/js2c/utility_init:5:364
callbackTrampoline @ internal/async_hooks:130:17
[JsonrpcGLSPClient] Connection to server is erroring. Shutting down server. (1) [Error: connect ECONNREFUSED 127.0.0.1:5007
	at TCPConnectWrap.afterConnect [as oncomplete] (node:ne…]
extensionHostProcess.js:100
arg1:
(1) [Error: connect ECONNREFUSED 127.0.0.1:5007\n\tat TCPConnectWrap.afterConnect [as oncomplete] (node:ne…]
f @ c:\Users\gvalenc\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:100:6
e @ c:\Users\gvalenc\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:96:138916
<anonymous> @ c:\Users\gvalenc\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:96:138784
error @ c:\Users\gvalenc\git\arf\solution-editor-vscode-extension\node_modules\@eclipse-glsp\protocol\lib\jsonrpc\glsp-jsonrpc-client.js:43:17
handleConnectionError @ c:\Users\gvalenc\git\arf\solution-editor-vscode-extension\node_modules\@eclipse-glsp\protocol\lib\jsonrpc\base-jsonrpc-glsp-client.js:93:49
<anonymous> @ c:\Users\gvalenc\git\arf\solution-editor-vscode-extension\node_modules\@eclipse-glsp\protocol\lib\jsonrpc\base-jsonrpc-glsp-client.js:88:41
invoke @ c:\Users\gvalenc\git\arf\solution-editor-vscode-extension\node_modules\vscode-jsonrpc\lib\events.js:62:39
fire @ c:\Users\gvalenc\git\arf\solution-editor-vscode-extension\node_modules\vscode-jsonrpc\lib\events.js:120:36
readErrorHandler @ c:\Users\gvalenc\git\arf\solution-editor-vscode-extension\node_modules\vscode-jsonrpc\lib\main.js:232:22
invoke @ c:\Users\gvalenc\git\arf\solution-editor-vscode-extension\node_modules\vscode-jsonrpc\lib\events.js:62:39
fire @ c:\Users\gvalenc\git\arf\solution-editor-vscode-extension\node_modules\vscode-jsonrpc\lib\events.js:120:36
fireError @ c:\Users\gvalenc\git\arf\solution-editor-vscode-extension\node_modules\vscode-jsonrpc\lib\messageReader.js:105:27
<anonymous> @ c:\Users\gvalenc\git\arf\solution-editor-vscode-extension\node_modules\vscode-jsonrpc\lib\messageReader.js:150:51
emit @ events:538:35
emitErrorNT @ internal/streams/destroy:157:8
emitErrorCloseNT @ internal/streams/destroy:122:3
processTicksAndRejections @ internal/process/task_queues:83:21
◀ TickObject ▶
init @ internal/inspector_async_hook:25:19
emitInitNative @ internal/async_hooks:201:43
emitInitScript @ internal/async_hooks:506:3
nextTick @ internal/process/task_queues:133:5
<anonymous> @ electron/js2c/utility_init:13:392
onDestroy @ internal/streams/destroy:96:15
Socket._destroy @ net:692:5
_destroy @ internal/streams/destroy:102:25
destroy @ internal/streams/destroy:64:5
afterConnect @ net:1166:10
callbackTrampoline @ internal/async_hooks:130:17
◀ TCPCONNECTWRAP ▶
init @ internal/inspector_async_hook:25:19
emitInitNative @ internal/async_hooks:201:43
internalConnect @ net:912:26
defaultTriggerAsyncIdScope @ internal/async_hooks:465:18
emitLookup @ net:1075:9
onlookup @ dns:73:8
callbackTrampoline @ internal/async_hooks:130:17
◀ GETADDRINFOREQWRAP ▶
init @ internal/inspector_async_hook:25:19
emitInitNative @ internal/async_hooks:201:43
lookup @ dns:157:21
<anonymous> @ net:1052:5
defaultTriggerAsyncIdScope @ internal/async_hooks:465:18
lookupAndConnect @ net:1051:3
Socket.connect @ net:989:5
start @ c:\Users\gvalenc\git\arf\solution-editor-vscode-extension\node_modules\@eclipse-glsp\vscode-integration\lib\quickstart-components\socket-glsp-vscode-server.js:64:21
activate @ c:\Users\gvalenc\git\arf\solution-editor-vscode-extension\client\src\extension.ts:408:17
processTicksAndRejections @ internal/process/task_queues:96:5
◀ await ▶
processTicksAndRejections @ internal/process/task_queues:96:5
◀ await ▶
processTicksAndRejections @ internal/process/task_queues:96:5
◀ await ▶
db @ c:\Users\gvalenc\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:108:14833
cb @ c:\Users\gvalenc\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:108:14532
<anonymous> @ c:\Users\gvalenc\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:108:12550
◀ Promise.then ▶
ab @ c:\Users\gvalenc\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:108:12470
Y @ c:\Users\gvalenc\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:108:11583
◀ await ▶
actualActivateExtension @ c:\Users\gvalenc\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:108:8591
n @ c:\Users\gvalenc\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:94:6831
m @ c:\Users\gvalenc\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:94:6792
◀ await ▶
l @ c:\Users\gvalenc\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:94:6249
f @ c:\Users\gvalenc\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:94:6176
k @ c:\Users\gvalenc\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:94:5656
j @ c:\Users\gvalenc\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:94:5611
<anonymous> @ c:\Users\gvalenc\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:94:4445
h @ c:\Users\gvalenc\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:94:4433
activateByEvent @ c:\Users\gvalenc\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:94:4110
R @ c:\Users\gvalenc\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:108:10026
<anonymous> @ c:\Users\gvalenc\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:108:20550
processTicksAndRejections @ internal/process/task_queues:96:5
◀ Promise.then ▶
$activateByEvent @ c:\Users\gvalenc\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:108:20536
N @ c:\Users\gvalenc\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:106:11223
M @ c:\Users\gvalenc\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:106:10941
H @ c:\Users\gvalenc\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:106:10034
G @ c:\Users\gvalenc\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:106:9015
<anonymous> @ c:\Users\gvalenc\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:106:7803
invoke @ c:\Users\gvalenc\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:63:145
deliver @ c:\Users\gvalenc\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:63:2066
fire @ c:\Users\gvalenc\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:63:1704
fire @ c:\Users\gvalenc\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:72:14907
<anonymous> @ c:\Users\gvalenc\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:122:16556
invoke @ c:\Users\gvalenc\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:63:145
deliver @ c:\Users\gvalenc\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:63:2066
fire @ c:\Users\gvalenc\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:63:1704
fire @ c:\Users\gvalenc\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:72:14907
<anonymous> @ c:\Users\gvalenc\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:122:14682
emit @ events:526:28
MessagePortMain._internalPort.emit @ electron/js2c/utility_init:5:364
callbackTrampoline @ internal/async_hooks:130:17
rejected promise not handled within 1 second: Error: Connection got disposed.
extensionHostProcess.js:100
stack trace: Error: Connection got disposed.
	at Object.dispose (c:\Users\gvalenc\git\arf\solution-editor-vscode-extension\node_modules\vscode-jsonrpc\lib\main.js:876:25)
	at c:\Users\gvalenc\git\arf\solution-editor-vscode-extension\node_modules\@eclipse-glsp\protocol\lib\jsonrpc\base-jsonrpc-glsp-client.js:73:24
	at process.processTicksAndRejections (node:internal/process/task_queues:96:5)

[tortmayr]

HI @gee4vee,
unfortunately we have not encountered a similar issue before. In theory it should not make any difference whether install the extension as vsix or via the extension host. It`s very strange that it only works for the vsix case.
Could you post the launch config that you are using for debugging? Maybe something is not configured correctly there.

[gee4vee]

@tortmayr I am now getting the connection refusal with the installed extension as well. Windows Firewall is off. I can see that the server is running and now and then after some restarts of vscode it works again. Is there a way for the JsonrpcGLSPClient to retry the connection? It could be the server isnt quite ready to accept the connection because it sometimes works if I wait a bit before opening the file that triggers the diagram.

2023-03-31 06:34:36.001 [error] [Extension Host] [JsonrpcGLSPClient] Connection to server is erroring. Shutting down server. [{"errno":-4078,"code":"ECONNREFUSED","syscall":"connect","address":"127.0.0.1","port":5007}]

[christianmalek]

Hello @gee4vee , you could find a solution for your problem?

[MassimoL06]

Hello, I am also having same issue on my computer on Windows 10 for VS Code integration.

[samadnasir23]

hey, have you managed to solve the problem I also have the same issue?

[MassimoL06]

Hello, unfortunatly no solution found until now !