Bloop server could not be started in WSL2 while compiling with `mill`
yuxuan-z19 opened this issue · comments
yuxuan-z commented
Describe the bug
- WSL version: 2.1.5.0 (with kernel 5.15.146.1-2)
- WSL2 OS: Ubuntu jammy
- Java version:
default-jdk
(openjdk 11.0.22 2024-01-16
) - Build tool:
millw-0.4.11
(mill-0.11.7
)
I'm compiling a SpinalHDL project using millw-0.4.11
(corresponding to mill-0.11.7
) on WSL2, and it should start and connect to a Bloop server, but it seems the server is not working until a timeout is raised.
metals.log
is provided here. Here is a quick screenshot:
I'd like to use the Vivado (Windows) so I put it under mnt/d
(using Windows filesystem perhaps?), does it matter?
Expected behavior
The build tool and the extension work perfectly on native Ubuntu jammy!
Operating system
Windows
Editor/Extension
VS Code
Version of Metals
v1.29.0
Extra context or search terms
No response