Closed KristianAN closed 1 month ago
Thanks for the report @KristianAN although nvim-metals really doesn't have anything to do with the import here. All it's down is setting the root and basically initializing Metals. The stack trace here is coming directly from Bleep and the BSP server here seems to be puking. So the issue here seems to lie somewhere between Metals <-> Bleep. Do you have an example project where this is happening that I can test?
Here is the project where I got the error. Which is just a initialized bleep project. https://github.com/KristianAN/migrator
So I just tested this both with VS Code and with nvim-metals and they both seem to fail with this result. Are you sure it doesn't have to do with Java version?
I don't think that Java version has anything to do with it. if I add //> using dep com.lihaoyi::fansi:0.5.0 to App.scala and run scala-cli setup-ide migrator metals imports the build without issue and everything works as expected
running echo $JAVA_HOME gives /nix/store/z16qjcmxxiki2ah8wvg4qp0kp96a5s84-temurin-bin-17.0.9 as expected by the flake.nix definition. It's very strange that it works in emacs and not other editors!
So I just tested this again with VS Code and I still get these errors. I'd recommend opening up an issue with Bleep and explaining because I don't see any reason how this can be associated to nvim-metals seeing that it happens for me with multiple clients.
I'm experiencing the same issue on my side
I'm experiencing the same issue on my side
This will be fixed in the next release of bleep.
Describe the bug
When trying to import the build after running setup-ide with bleep it fails to import the project with the following stacktrace
I have tested it with Emacs lsp-mode where it works fine (have not tested vscode, but I assume it works fine there)
Expected behavior
Builds are imported in nvim-metals with bleep like other editors.
Operating system
Linux
Version of Metals
1.3.0
Commit of nvim-metals
4f9bf0c821092f20dd34c1a4ea5b07b0500ff089