Katarzyna Marek

Since https://github.com/scalameta/metals/pull/6044, we always compile on `didFocus`, `didOpen` if the build target in focus changed to avoid complicated logic with keeping track of which inverse dependencies are influenced by previous...

I see what you mean, I'm just not sure how to handle this reasonably. > So even in that scenario no matter what compilations are triggered? Yes, every time build...

Fixed in bloop.

> However the server should read the SBT_OPTS when started by the BSP command. It is a bug if it does not. That seems to work as expected. > I...

> My suggestion would be to change the way sbt generates the BSP config. How should we generate the config then? We generate it running `.../sbt bspConfig` wouldn't that be...

Oh, yeah, sorry. I misread what you wrote.

It seems we always recompile the build target and wait for the compilation to finish before evaluating the worksheet, and I can't reproduce this behaviour. If this is still an...

I don't think we should remove it. The failing suite `DebugProtocolSuite` is flaky and should probably be marked as such, so it doesn't stop the CI from passing.

> the tests are successful, but how do I manually test it? publishLocal;mtags/publishLocal doesn't seem to work and there's errors in metals log like: Error downloading org.scalameta:mtags_2.12.18:1.2.1-SNAPSHOT I'm guessing you're...

> does quick-publish-local make it work for major versions like 2.12, 2.13, 3 You can find all the quick publish versions here: https://github.com/scalameta/metals/blob/e65409f2d77655def76e705c3c0320da7544c345/project/V.scala#L136 but `2.12.18`, `2.13.12`, and `3.3.1` are included.