Modular•13mo ago

VSCode extension not working on Linux

The output error is:

2023-09-08 21:12:09.901 [error] TypeError: The argument 'options' must have the property "port" or "path". Received {}
    at new NodeError (node:internal/errors:387:5)
    at Server.listen (node:net:1615:11)
    at /home/teampuzel/.vscode/extensions/modular-mojotools.vscode-mojo-0.2.1/out/debug/externalDebugLauncher.js:177:54
    at new Promise (<anonymous>)
    at RpcLaunchServer.<anonymous> (/home/teampuzel/.vscode/extensions/modular-mojotools.vscode-mojo-0.2.1/out/debug/externalDebugLauncher.js:177:20)
    at Generator.next (<anonymous>)
    at /home/teampuzel/.vscode/extensions/modular-mojotools.vscode-mojo-0.2.1/out/debug/externalDebugLauncher.js:13:71
    at new Promise (<anonymous>)
    at __awaiter (/home/teampuzel/.vscode/extensions/modular-mojotools.vscode-mojo-0.2.1/out/debug/externalDebugLauncher.js:9:12)
    at RpcLaunchServer.listen (/home/teampuzel/.vscode/extensions/modular-mojotools.vscode-mojo-0.2.1/out/debug/externalDebugLauncher.js:176:16)
    at MojoDebugContext.updateOrCreateRpcServer (/home/teampuzel/.vscode/extensions/modular-mojotools.vscode-mojo-0.2.1/out/debug/debug.js:82:19)
    at new MojoDebugContext (/home/teampuzel/.vscode/extensions/modular-mojotools.vscode-mojo-0.2.1/out/debug/debug.js:64:18)
    at MOJOContext.<anonymous> (/home/teampuzel/.vscode/extensions/modular-mojotools.vscode-mojo-0.2.1/out/mojoContext.js:68:35)
    at Generator.next (<anonymous>)
    at fulfilled (/home/teampuzel/.vscode/extensions/modular-mojotools.vscode-mojo-0.2.1/out/mojoContext.js:10:58)

2023-09-08 21:12:09.901 [error] TypeError: The argument 'options' must have the property "port" or "path". Received {}
    at new NodeError (node:internal/errors:387:5)
    at Server.listen (node:net:1615:11)
    at /home/teampuzel/.vscode/extensions/modular-mojotools.vscode-mojo-0.2.1/out/debug/externalDebugLauncher.js:177:54
    at new Promise (<anonymous>)
    at RpcLaunchServer.<anonymous> (/home/teampuzel/.vscode/extensions/modular-mojotools.vscode-mojo-0.2.1/out/debug/externalDebugLauncher.js:177:20)
    at Generator.next (<anonymous>)
    at /home/teampuzel/.vscode/extensions/modular-mojotools.vscode-mojo-0.2.1/out/debug/externalDebugLauncher.js:13:71
    at new Promise (<anonymous>)
    at __awaiter (/home/teampuzel/.vscode/extensions/modular-mojotools.vscode-mojo-0.2.1/out/debug/externalDebugLauncher.js:9:12)
    at RpcLaunchServer.listen (/home/teampuzel/.vscode/extensions/modular-mojotools.vscode-mojo-0.2.1/out/debug/externalDebugLauncher.js:176:16)
    at MojoDebugContext.updateOrCreateRpcServer (/home/teampuzel/.vscode/extensions/modular-mojotools.vscode-mojo-0.2.1/out/debug/debug.js:82:19)
    at new MojoDebugContext (/home/teampuzel/.vscode/extensions/modular-mojotools.vscode-mojo-0.2.1/out/debug/debug.js:64:18)
    at MOJOContext.<anonymous> (/home/teampuzel/.vscode/extensions/modular-mojotools.vscode-mojo-0.2.1/out/mojoContext.js:68:35)
    at Generator.next (<anonymous>)
    at fulfilled (/home/teampuzel/.vscode/extensions/modular-mojotools.vscode-mojo-0.2.1/out/mojoContext.js:10:58)

3 Replies

Краси•12mo ago

May the plugin need any requirements that we dont meet ? Do you think this is due to our configuration or everyone is seeing this error message too? They didn't have it during the demonstration.

TeamPuzel•12mo ago

There's a github issue on this, the reason the extension breaks is because the language server freezes when you have less than 16gb of memory They're going to have to work on it to lower the requirements

TeamPuzel•12mo ago

https://github.com/modularml/mojo/issues/680

GitHub

[BUG]: Completions hanging on systems with low RAM · Issue #680 · m...

Bug description It appears to only occur on systems with RAM at 8GB or less, even though it doesn't appear the RAM is completely depleted, the extension hangs when trying to use any completions...

Gaming

Programming

VSCode extension not working on Linux