Bloop coursier problems in company environment

[kmakiela96]

Metals Visual studio code extension downloads coursier dependencies from company artifactory with authorization, but unfortunately when bloop tries to download semanticDb dependency i receive unauthorized response. What can I do? How to make bloop coursier properly use credentials?

[tgodzik]

It might be possible to modify the bloop metals.bloopJvmProperties to include the needed properties 🤔

The defaults are:

"metals.bloopJvmProperties" : [
   "-Xss4m",
      "-XX:MaxInlineLevel=20", // Specific option for faster C2, ignored by GraalVM
      "-XX:+UseZGC", // ZGC returns unused memory back to the OS, so Bloop does not occupy so much memory if unused
      "-XX:ZUncommitDelay=30",
      "-XX:ZCollectionInterval=5",
      "-XX:+IgnoreUnrecognizedVMOptions", // Do not fail if an non-standard (-X, -XX) VM option is not recognized.
      "-Dbloop.ignore-sig-int=true"
]

so you might add the needed coursier property.

[kmakiela96]

The commands are not working, I'm getting not found, I've restarted the server by restarting vs code

[tgodzik]

There is a separate command to restart build server since it's a separate process being used for all workspaces. If it wasn't restarted at any point it will not use any new parameters.

[kmakiela96]

all of vs code metals commands are not working

[tgodzik]

That's unexpected, does the server start at all?

[kmakiela96]

no, because it want's to set up bloop first, but bloop cannot download it's dependencies. The server ends with internal server error and cause is that internal coursier in bloop cannot download dependencies because it receives unauthorized. Why metals have to use bloop even if I have project set in sbt or bazel? It seems like an unnecessary thing

[kmakiela96]

Seems like maybe it's an issue that should be reported, unless there is already one similar, is there any?

[kmakiela96]

Is it possible to switch to sbt before metals tries to set up bloop? I'm not sure why the commands are not working

[tgodzik]

You can always switch to using just sbt with Switch build server command. Though, you need to currently onvoke it via command prompt in VS Code. I added it to metals view, but that will be available with the next version of metals.

[kmakiela96]

I cannot invoke the command because server doesn't start at all, because metals whant to set up bloop first no matter what

[kasiaMarek]

There is also a setting, so if you have sbt it should start sbt instead of bloop.

But note that this will work only on a fresh project. Meaning one, where Metals did not save any of your choices of build server.
Such choices would be saved in the .metals directory, so you can just manually delete the directory. For fuller clean you should also delete project/metals.sbt, project/project/metals.sbt and so on (Metals adds some plugins to sbt).

[kmakiela96]

No such folder and files are in my project. I've already selected the setting which you pasted here

[tgodzik]

Btw. do you get the same stack trace as in https://github.com/scalameta/metals-vscode/issues/1600 ?

[kmakiela96]

Unfortunately our corporate artifactory couldn't find the snapshot version, it mirros maven central but maybe without snapshots?

[kmakiela96]

Ah, on maven central I cannot find snapshot version either

[bartoszkosiorek]

Is it possible to release Release Candidate, so it will appear in Maven Central?
https://mvnrepository.com/artifact/org.scalameta/metals
Then the solution could be verified.

[tgodzik]

We can just release a full version and if that doesn't work I will go ahead with RC or just next versions

[kmakiela96]

that would be nice, thx :)

[kmakiela96]

metals 1.5.2 works fine, thank you very much for fixing this ❤️