Extension (v0.30.0) not working on a Linux desktop (Ubuntu 22.05) using VSCode

[davidnind]

I attempted to use the vale-vscode extension (0.30.0) with VSCode on an Ubuntu 22.04.5 LTS desktop.

It looks like there are issues running the Vale Language Server.

I've attached the error log when VSCode starts up (after installing the extension and restarting VSCode): error log when starting VSCode on an Ubuntu 22.04.5 desktop

One solution may be to update my desktop to a later version. I will report if it is still an issue when do this.

Note: I tested on Windows 10 and it worked fine without any issues (fresh VSCode installation, the latest vale, and version 0.30.0 of the extension).

[frimik]

On Linux you get the wrong binary installed for the Vale language server:

file .vscode-server/extensions/chrischinchilla.vale-vscode-0.30.0/vale-ls
.vscode-server/extensions/chrischinchilla.vale-vscode-0.30.0/vale-ls: Mach-O 64-bit arm64 executable, flags:<NOUNDEFS|DYLDLINK|TWOLEVEL|PIE|HAS_TLV_DESCRIPTORS>

[ChrisChinchilla]

@frimik and @davidnind This was tested successfully by a few people on different Linux setups, so any chance you could both tell me (if not already)…

• Linux distribution and version
• CPU architecture

[ctjdr]

Same here with:

$ uname -i
x86_64

$ lsb_release --description
No LSB modules are available.
Description:	Ubuntu 24.04.2 LTS

[davidnind]

Here are my detail (Ubuntu 22.04 LTS, x86_64):

$ uname -i
x86_64

$ lsb_release --description
Description:	Ubuntu 22.04.5 LTS

[frimik]

Same (Ubuntu 22 on WSL actually, but not important).

If I remove everything and have it download things again, I get a different binary this time.

I ran this extension source code in debugger, with slightly modified outputs:

First launch: Downloading Vale Language Server from URL: https://github.com/errata-ai/vale-ls/releases/download/v0.4.0/vale-ls-x86_64-unknown-linux-gnu.zip

And that file is correctly chosen for the arch. But it's not a great distribution binary. So maybe the original issue with me getting a MacOS binary was due to wrong packaging... my vale-vs has been broken in the background for a while, and I had very high uptime in my vscode, so I'm not entirely sure exactly what date this problem originally occured to be honest.

So, let's just move forward... the MacOS problem is no more, it's just a "poorly" distributed binary, if I'm allowed to say:

# file vale-ls
vale-ls: ELF 64-bit LSB pie executable, x86-64, version 1 (SYSV), dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, BuildID[sha1]=80842559373b03488701aa7efc9ab991dfb5d0b5, for GNU/Linux 3.2.0, not stripped
# ./vale-ls
./vale-ls: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.38' not found (required by ./vale-ls)
./vale-ls: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.39' not found (required by ./vale-ls)

[barstown]

Similar issue here on a VDI environment running Ubuntu 22.04 LTS, x86_64, and also on on my home workstations running Fedora. The personal workstations both got a fresh install when 42 came out last month.

$ uname -m
x86_64

$ cat /etc/redhat-release
Fedora release 42 (Adams)

Like some others here, it appears to have incorrectly downloaded the arm binary for my system.

file vale-ls
vale-ls: Mach-O 64-bit arm64 executable, flags:<NOUNDEFS|DYLDLINK|TWOLEVEL|PIE|HAS_TLV_DESCRIPTORS>

[ChrisChinchilla]

Okay, thanks, everyone. It looks like all that information makes it easier to see what the issue is, and I hope to have a fixed version by the end of the week.

[ChrisChinchilla]

Hello all and @davidsneighbour

This is very odd… As many of you have found, if you install, then the macOS binary for vale-ls is installed, if you find the code for the extension, which seems to generally be in the home folder > .vscode > then the extension path and delete the current vale-ls file, then resave or reload and the extension redownloads the correct binary 🤷 .

I am very confused by this 😆 and am trying to figure out what on earth is happening… But in the meantime taking those slightly annoying steps seems to get it working. I assume some sort of node async race condition, but that is very hard to debug, so leave it with me…

It also doesn't seem to be an issue on macOS or Windows, both of which also have different binaries available, so it's all quite strange.

As any kind of indicator you can run file to check it's the right architecture, or on Linux on ARM at least, the file size should be about 16mb, whereas the macOS one is about 10mb.

[sandrobonazzola]

Same issue on Fedora 42. 0.20.0 worked fine while 0.30.0 is failing on vale-ls being aarch64 while the cpu is a x86_64.

Removing the vale-ls wrong executable trigger the downloading of a new executable at next run. The new executable is for the correct architecture.

[ChrisChinchilla]

Hey all v0.30.1 should fix this, but it's very hard for me to test and involves a series of SSH and devcontainer tunnels that I am not 100% sure of. But if this now does work I can move on to other tasks knowing that this part is complete.

To be fully sure, you might need to uninstall the extension and re-install it, so I can see if the correct binary is downloaded. Any help with checking that is appreciated! 👏

[sandrobonazzola]

Works for me with 0.30.1 on Fedora 42.

[davidnind]

Thanks!

It looks like the correct binary is now downloaded for me (Ubuntu 22.04).

file vale-ls
vale-ls: ELF 64-bit LSB pie executable, x86-64, version 1 (SYSV), dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, BuildID[sha1]=80842559373b03488701aa7efc9ab991dfb5d0b5, for GNU/Linux 3.2.0, not stripped

However, it looks like I will still need to do an operating system upgrade at some stage as I get a glibc version error:

The Vale VSCode server crashed 5 times in the last 3 minutes. The server will not be restarted. See the output for more information.
/home/david/.vscode/extensions/chrischinchilla.vale-vscode-0.30.1/vale-ls: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.38' not found (required by /home/david/.vscode/extensions/chrischinchilla.vale-vscode-0.30.1/vale-ls)
/home/david/.vscode/extensions/chrischinchilla.vale-vscode-0.30.1/vale-ls: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.39' not found (required by /home/david/.vscode/extensions/chrischinchilla.vale-vscode-0.30.1/vale-ls)

[ChrisChinchilla]

@davidnind Hmm, not wanting to pass the buck, but this is an issue with the underlying vale-ls binary, so it looks like the extension issue is resolved and I will move this issue to there and see what we can do about it