Package Details: mesonlsp 5.0.3-1

Git Clone URL: https://aur.archlinux.org/mesonlsp.git (read-only, click to copy)
Package Base: mesonlsp
Description: Meson language server
Upstream URL: https://github.com/JCWasmx86/mesonlsp
Licenses: GPL-3.0-or-later
Submitter: polyzen
Maintainer: Ordoviz (fam007e)
Last Packager: Ordoviz
Votes: 2
Popularity: 0.73
First Submitted: 2025-10-27 15:34 (UTC)
Last Updated: 2026-05-25 09:14 (UTC)

Latest Comments

fam007e commented on 2026-04-27 16:10 (UTC)

I added a patch to fix the stderr deadlock. Now it installs the normal way.

At1ass commented on 2026-04-27 14:46 (UTC)

Build with MESONLSP_NO_LOG=1 fix the issue with lsptest

v1993 commented on 2026-04-27 07:54 (UTC)

Tests continue to fail due to lsptest timing out, unfortunately, but the LSP seems to work okay now.

fam007e commented on 2026-04-26 21:09 (UTC)

Build fails at check() with lsptest timing out (30s). The test hangs because the server crashes immediately on startup before responding to the LSP initialize request.

Running the server manually confirms the issue:

  echo '{"id":1,"method":"initialize","params":{"capabilities":{},"rootUri":null,"workspaceFolders":[]},"jsonrpc":"2.0"}' | src/mesonlsp --lsp

The server scans packages successfully, then crashes with:

  std::future_error: No associated state
  terminate called after throwing an instance of 'std::future_error'
  zsh: IOT instruction (core dumped)

Stack trace points to a std::future object being accessed without an associated state, likely in the new async workspace initialization code introduced in 5.0.0.

Also worth noting: the meson.build inside the repo still reports Project version: v4.3.7 despite being tagged v5.0.0, which suggests the tag may have been pushed prematurely.

Workaround for now is to add mesonlsp to IgnorePkg in /etc/pacman.conf and stay on 4.3.7. Upstream bug filed at https://github.com/JCWasmx86/mesonlsp/issues/192