Open KAction opened 3 years ago
For what it worth, just upgraded Debian box to Sid (debian 5.14.0-4-amd64), and it still does not work.
cc @maralorn
I am honestly no expert in regard to OS details. In general I think hls shouldn‘t hang, no matter how weird the environment it’s in. So this is probably a bug worth reporting upstream? Have you tried to install hls via other means (e.g. ghcup) and witnessed a different behavior? One possible problem I can think of would be if you have a ghc or cabal from the host system in your environment. That could cause trouble. (But still, it shouldn‘t hang.)
I tried building using stack(1), but it complains that no binary distribution found for my (libc, curses) version. I tried to rebuild on my hls on my box from Nix sources (substitute = false) with no avail.
I tried building using stack(1), but it complains that no binary distribution found for my (libc, curses) version. I tried to rebuild on my hls on my box from Nix sources (substitute = false) with no avail.
Have you tried with just cabal? Also you might have ABI issues, this script might help you determine if so:
Describe the bug
I have several systems, running inside Virtual Box with MacOS host, all of them running Nix. On one of them (Void Linux, linux=5.13.13_1) haskell-language-server works as expected, on two others -- Debian stable (5.10.0-9-amd64) and custom distribution (linux=5.15.2) it hangs with following strace:
I am somewhat stuck how to debug further. Any chance that GHC generates code that makes some assumptions about kernel, given that box that works has the freshest kernel? Or any other ideas.
For what it worth, it also works correctly on host MacOS ( 20.6.0 Darwin Kernel Version 20.6.0).
A clear and concise description of what the bug is.
Steps To Reproduce
Steps to reproduce the behavior:
Expected behavior
haskell-language-server do not hang at step 4. This is how it looks like at boxes where it works:
and this is how it looks like at boxes where it does not work:
Metadata
This is output of
nix-shell -p nix-info --run "nix-info -m"
on problematic Debian box.Maintainer information: