Unable to make a BSP connection with Bloop #2207
Comments
|
Thanks for the report @jqno! So it's not specifically a coc-metals issue, but let's see if we can get it tackled first. We've seen this in a few places, and it's odd that Bloop is behaving this way. Do you have Bloop CLI installed? If possible, there is a couple things you can try to help this out. Firstly, make sure you're on the latest, which is > 1.4.5. With the new version of Metals you want to make sure you're not still on 1.4.4.x You can check this with a Also, looking again at the logs, Metals 0.9.4 will try the BSP connection once, and then time out. 0.9.5 has a built-in retry. So it's best to try with that. Again, if I had to guess, it would be that you still have an old Bloop running. |
ckipp01
changed the title
|
Thanks for the quick response! I've updated back to the most recent version of coc-metals (current commit) and done the things you said. According to the metals.log file, it's now on Metals version 0.9.5. Indeed, I have Bloop CLI 1.4.4 installed locally through Coursier. (Maybe I should remove it? I never run it directly.) When I do So it seems like that is using the more recent version of Bloop, but it still ends up in the same stacktrace. |
If you have it installed vial |
|
I've updated bloop as you said, it's now at 1.4.5.something. I only see it retrying twice, though. Relevant sections of the log: |
|
Thanks for reporting! Is this problematic in every workspace or just one? Did you try removing |
|
I've tried in 2 workspaces, one maven and one sbt. I've removed these directories several times, but it didn't help. I haven't done an in depth comparison between the two workspaces, but the effects seem the same. |
|
The weirdest thing is that it used to work for you without problems. Did you maybe change the default java version? Was there anything at all that you changed aside from Metals version? Especially if you reverted it should just go back to normal. Could you try running with |
tgodzik
added
the
needs more information
|
Thanks for all the help, @ckipp01 and @tgodzik. I'm a little embarrased to say, after a restart of my machine, everything worked perfectly again. Should've thought about this earlier, I work in IT after all 😅 Just to give you all the information that you asked for, in case it may be of help later:
This morning, I restarted my machine to install a software update (no, not the Big Sur one yet, I'll wait a bit before I do that one 😉) and things worked again, both in my Maven project and my SBT project. |
🎉 ha, glad it's working!! Although, again, it's not ideal that this happened in the first place. Thanks for all the info that you have us. The issue you described is something we're aware of and have seen pop up a couple times. We do have some ideas and things that we'll be trying to remedy this situation where a user is simply unable to connect to the server. So hopefully these situations will be become more rare. If you have this happen again, feel free to pop in here and let us know. |
|
Thanks, I will let you know if I run into it again. In the mean time, if there's something I can do to help with this, please let me know! |
|
I experienced exactly the same issue: And after much debugging and arriving at this page I can confirm that simply restarting the machine did the trick. |
|
I've got the same problem when I killed and relaunched my emacs. I noticed that bloop process still works and metals can't connect to them. If kill this bloop process everything will work and do reboot isn't necessarily |
Question
I saw on twitter there's a new release of coc-metals, so obviously I wanted to upgrade. After the upgrade though, the Metals server no longer starts for me. I reverted to the previous version, and it still doesn't start. Happens both on Maven and SBT projects.
I'm not sure if this is a Metals issue or a coc-metals issue, so I picked one. I'm happy to move this issue if I picked incorrectly :)
Installation:
08190437e386c3841eaaa0c033ca4ee381d7eb78-- I think that corresponds to 0.0.79eb0e501bd74bda475f463af5b7b645f639cf28ad-- I think that corresponds to 0.9.5Additional context
I've tried adding an explicit
metals.javaHomeentry to make sure that the correct JVM is used, but it doesn't seem to help. It's managed with sdkman.io, if that's relevant.Here's (part of) the content of my
.metals/metals.logfile:Search terms
The text was updated successfully, but these errors were encountered: