Open divijan opened 5 months ago
Thanks for reporting! I might have a potential fix in https://github.com/scalameta/metals-vscode/pull/1510 though we had some issues with adding properties to native image before. Will need to confirm.
Looks like we couldn't add the java properties automatically since there seems to be a bug with coursier native image in Windows. Could you try adding JAVA_OPTS variable with "-Dfile.encoding=UTF-8" set? Let's see if that helps.
The alternative is to use old jar launcher when this happens.
I've set this variable through control panel and it didn't help. Tried option with and without quotes. When I install Java 17 as a normal Windows package, I get the error described in https://github.com/scalameta/metals-vscode/issues/366. Is it caused by the same glitch in coursier?
It's an issue with encoding, if we set it it should work correctly, but there seems to be an issue here with setting it. I am doing a workaround in the PR linked here.
Updated to metals 1.3.5 and metals-vscode 1.39.0. With or without Java 17 installed, the error messages are the same, corresponding to what I wrote above. Seems to me if you are a developer, writing your username in cyrillic characters in Windows is a bad idea. Had something else fail because of this yesterday.
Exactly the same? I hoped that the workaround would help, but then I will need to reproduce it locally on a windows machine :thinking:
Pretty much. With Java 17 not installed, exactly the same save the versions, and with Java installed, very little difference. Do you want me to produce the actual output?
Unable to start Metals extension with cyrillic characters in path under Windows Cannot find java executable in path with cyrillic characters in it.
Metals Extension output:
To Reproduce:
Expected behavior
VS Code should be able to start the server because the
java
executable is there, the launcher can't seem to understand the cyrillic characters in the path.Installation:
metals.serverVersion
) 1.3.1Additional context
After I have 'officially' installed JDK 17 under Program Files, the problem has shifted its shape to this:
I found a similar problem described here. It is claimed to be fixed, but apparently not for all cases.
Search terms
Launching server using command ... failed., Error: Spawn ... ENOENT, cyrillic