unfortunately this should have been the "current" value, and not the percentage, i.e. the current/total, otherwise metals will try to render e.g. 95%/50 for project foo and report foo - 30s (190%), or pretty much be stuck at zero for large modules

I propose two fixes:

• we can report the "current" correctly, but I think the kind should be updated to "compile-progress2" (or "sbt-progress") to preserve compatibility
• metals client/whatever when they receive a build/taskProgress of kind "compile-progress" they must ignore the "total" field from the notification, and fix it to always be 100.

How does IntelliJ handle it? How does it handle bloop-progress? Can we do the same in Metals?

It looks like IntelliJ ignores the kind field:
https://github.com/JetBrains/intellij-scala/blob/5100ec6250070db147f409af755e08a75873e1a3/bsp/src/org/jetbrains/bsp/project/BspTask.scala#L298

I can only see that it prints the message field in the build window

Ok then I think we should fix this in sbt so that it is consistent with Bloop.

ok but I still propose that we change the kind of the event, this way metals will always be correct, as it can handle the old kind the old way