-
Notifications
You must be signed in to change notification settings - Fork 79
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Metals does not start anymore on Windows in VS Code since the VS Code extension v1.30.0 #1488
Comments
Downgrading to the VS Code extension v1.29.0 solved the issue, even though it uses Metals 1.3.0 anyway. So this seems to be related to v1.30.0 of the VS Code extension, in fact. |
It looks like we have a timeout inside one of the dependencies which causes the Metals never to find proper Java home. I removed that library in the prerelease, could you try it out? |
@sjrd could you try the latest prerelease? |
I haven't had much time on a Windows machine since my report. I can try tomorrow evening. |
I have the same issue on Mac. Switching to pre-release didn't work. Only downgrading to 1.29 works |
@sebastianmarkowski what shows up in your logs? It should not hang the same way since we removed the library that was hanging. |
I also just merged another fix that will fall back to java on PATH. So that should be even safer, do let us know what shows up for you if that still doesn't work. If it works I will release 1.31.0 later on. |
@tgodzik
|
Looks like it's another issue and the coursier fails to properly download 🤔 What is you operating system? |
Ach ok nvm, I see it's mac |
This might have been a problem with a download, we could add a retry, does it happen every time for you? |
Every single time. |
Maybe you would be able to run this manually and get more error messages: |
So it's the same message minus the "failed to fetch" My Mac is 12.4 which I can't update due to company policy |
Maybe it's an issue with gzip version? Looks like the only way yo work around it is to fallback to use coursier.jar as previously, but that will only work if JAVA_HOME is set. |
I also have the same problem with VS Code on my Mac(14.4.1). @tgodzik Thanks |
I wanted to fix one more thing, but you're right, we should do a new release with the current fixes. Will do it Sunday or Monday, sorry about that! |
I release a new version, do let me know if it works. |
Thank you so much @tgodzik |
Glad to hear it! |
It still doesn't work for me, so I guess there's an issue with older mac version. It would be cool if there was some way to specify max version for an extension depending on operating system. |
What is an error you are getting? I need to still do another workaround |
The exact same. Nothing changed for me. |
@smarkess did you already try uninstall the plugin and reinstall? Initially it didn't work for me as well. Then I uninstalled plugin and deleted metadata files. Then it worked for me . Thought it might be some coincidence and ignored it |
@yadavan88 |
I am still encountering this issue using version 1.31.0. |
@hhucchenyixiao the problem the same as in the description of the issue? |
|
Could you check Output (metals) if there is any info? |
@tgodzik Working mac: Macbook air - 12.7 (attaching the screenshot) |
Sorry for the radio silence. v1.31.0 works fine over here on Windows. Thank you :) |
The fallback to the old way of fetching metals has been added back. Can anyone having issues let us know if that fixed something? You need to switch to newest prerelease. |
@tgodzik |
@yadavan88 could you check Metals output to see what is being logged? View -> Output and choose Metals in the dropdown. |
Hi @tgodzik
After that when I click on "start metals", nothing logs |
Looks like coursier is actually old and unable to resolve adopt as a default, which does not hava Java 17 indeed. Does |
ok, this should fix it then #1500 |
You should be able to try it out again. |
@tgodzik
I have JAVA_HOME setup in both .zshrc and .bash_profile. Also, before (1.29.0) it didn't have problems finding JAVA_HOME. But at the very least it doesn't fail silently like before and instead shows error popup with JAVA_HOME message. |
@smarkess you can change the version of Java required by Metals to be 11. We try to find 17 by default, which is why we are not picking up the local 11.
|
@tgodzik |
@tgodzik |
As a workaround you can try to update coursier. I will look into what is happening a bit later |
Thanks, it works fine after coursier update |
I missed one place with my previous fix #1503 |
Describe the bug
I (automatically) updated Metals in VS Code to the latest release from April 15 on a Windows machine. Now Metals just ... does not start anymore. No "Starting Metals". The Metals tab shows the "New Scala project" and "Start Metals" blue buttons, but clicking on them does not do anything. No logs that I can find either. No
.metals
directory. It's almost as if it is not even there. I don't even get syntactic help like auto-indent on Enter after an=
.Things I tried:
.bsp
/.vscode
/.metals
from beforeOn my Linux machine at work I haven't observed any issue.
Expected behavior
Er ... at least show me an error message I guess? Ideally successfully start.
Operating system
Windows
Editor/Extension
VS Code
Version of Metals
v1.3.0
Extra context or search terms
No response
The text was updated successfully, but these errors were encountered: