Auto connection for custom BSP doesn't work
name-snrl opened this issue · comments
Describe the bug
I'm using https://github.com/ValdemarGr/mezel as custom bsp. Since #6164 auto connection has stopped working. During startup metals writes in the log that Build server is not auto-connectable, that's it, nothing further happens. If I restart the build server, everything starts working as normal
Expected behavior
metals connects to mezel on startup
Operating system
Linux
Editor/Extension
Nvim (nvim-metals)
Version of Metals
1.2.2+98-353c8887-SNAPSHOT
Extra context or search terms
2024.03.27 15:44:57 INFO Started: Metals version 1.2.2+98-353c8887-SNAPSHOT in folders '/home/yusup/backend' for client Neovim 0.10.0-dev.
SLF4J: Class path contains multiple SLF4J providers.
SLF4J: Found provider [scribe.slf4j.ScribeServiceProvider@661629d6]
SLF4J: Found provider [ch.qos.logback.classic.spi.LogbackServiceProvider@58a8c52]
SLF4J: See https://www.slf4j.org/codes.html#multiple_bindings for an explanation.
SLF4J: Actual provider is of type [scribe.slf4j.ScribeServiceProvider@661629d6]
2024.03.27 15:44:57 WARN Flyway upgrade recommended: H2 2.2.224 is newer than this version of Flyway and support has not been tested. The latest supported version of H2 is 2.2.220.
2024.03.27 15:45:00 WARN Build server is not auto-connectable.
2024.03.27 15:45:13 DEBUG Resolved mtags for 3.3.3
2024.03.27 15:45:13 INFO no build target found for /home/yusup/backend/modules/server/main/scala/services/Service.scala. Using presentation compiler with project's scala-library version: 3.3.3
2024.03.27 15:46:04 INFO Shutting down server
2024.03.27 15:46:04 INFO shutting down Metals
2024.03.27 15:46:04 DEBUG Saving 1 fingerprints for /home/yusup/backend/modules/server/main/scala/services/Service.scala