You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
During today's upgrade from 1.3.5 to 1.4.0, I noticed that compilation of our projects just stopped compiling after a couple of projects. After looking at the bloop errors, I decided to remove WartRemover from our environment to see if that was cousing the issue. Once removed, Metals started working again.
It looks to be the same problem as scalacenter/bloop#1421 and is a blocker for upgrading for us. We'll revert to 1.3.5 until such time that we have a solution.
We ran into the same issue. There is an even smaller reproduction (hello world essentially) that I reported on discord. I'll paste it here. Maybe someone will find it useful:
Compiler quits with Wartremover Enabled
During today's upgrade from 1.3.5 to 1.4.0, I noticed that compilation of our projects just stopped compiling after a couple of projects. After looking at the bloop errors, I decided to remove WartRemover from our environment to see if that was cousing the issue. Once removed, Metals started working again.
I removed the following:
I've included the errors we were seeing.
reports.zip
Here are another set of errors after removing wartremover, but Metals does seem to work.
reports_removed_wartremover.zip
Expected behavior
I expect Metals to be tolerant of Wartremover, and continue to compile all of the code.
Operating system
Linux
Editor/Extension
VS Code
Version of Metals
v1.4.0
Extra context or search terms
wartremover
The text was updated successfully, but these errors were encountered: