search

idaholab / moose-language-support

MOOSE language support for VSCode
Other
5 stars 4 forks source link

vscode 1.82 cannot connect to the moose language server in WSL #15

Closed Ramzy1990 closed 1 year ago

Ramzy1990 commented 1 year ago

I encountered the following error on vscode 1.82:

RuntimeError: abort(TypeError: Failed to parse URL from /home/ramzy/.vscode-server/extensions/danielschwen.moose-language-support-0.6.1/server/node_modules/web-tree-sitter/tree-sitter.wasm). Build with -s ASSERTIONS=1 for more info.
    at process.we (/home/ramzy/.vscode-server/extensions/danielschwen.moose-language-support-0.6.1/server/node_modules/web-tree-sitter/tree-sitter.js:1:11339)
    at process.emit (node:events:513:28)
    at emit (node:internal/process/promises:149:20)
    at processPromiseRejections (node:internal/process/promises:283:27)
    at process.processTicksAndRejections (node:internal/process/task_queues:96:32)

Node.js v18.15.0
[Error - 3:47:37 PM] Connection to server got closed. Server will not be restarted.

This error appears while using either the 0.6.0 or the updated 0.6.1 (and even the 0.5.1) on WSL through a vscode server. Tried it on different WSL Linux distributions (Ubuntu-22.04 and Ubuntu-23.10 (through Ubuntu-Preview)).

Downgrading to vscode 1.81 solves this problem. It seems to be related with upgrading Node.js to version 18 from 16 in the latest vscode 1.82 as explained here.

dschwen commented 1 year ago

Thanks for reporting this. I'll have a look.

dschwen commented 1 year ago

Ok, check v0.6.2 it works for me in VSCode 1.82

Ramzy1990 commented 1 year ago

Thank you for the prompt hotfix! The main issue has been solved, but now the "Malformed Input." warning appears whenever an input file is saved, even if it confirms to the hit file check (supposedly). I think opening a new issue for this is better.