Alec Theriault

Here's another example with less processes running. Taken at the same time, here's the JPS output: ``` 35523 Jps 34469 MyLanguageServer 2666 BloopServer 2874 MyLanguageServer 2875 MyLanguageServer 34203 Main 34411...

> Not entirely sure, but it seems there is a lot of IO activity forwarding outputs from those programs. Might be worth eliminating running them and see if that is...

I ended up generating manifest JARs (much like I think Metals does) by first creating a short-lived Bloop client which just makes a couple queries to determine the runtime classpath...

Thanks for the pointer. Normally `allOrThrow(statusCodes)` is fine because `Keys.bspBuildTargetCompileItem` already handles catching `Compile` errors and turning them into the right status code: https://github.com/sbt/sbt/blob/978dd5779dc9f17d19cd1d07229215a570739dc3/main/src/main/scala/sbt/internal/server/BuildServerProtocol.scala#L792-L796 I did some quick poking with...

What you say makes sense, but shouldn't it be `bspBuildTargetCompileItem` that does the catching of the exception? It is a task that is supposed to produce the BSP status code...

Yeah, I'm not surprised to hear this might blow up the size of the bloom filters. An option would be nice to at least try it out... I also would...

Coming back to this request, I still think this would be a big improvement. When I'm working on code I very often want to be searching through my dependencies and...

> Unfortunately, I'm not sure the BSP provides a good way to distinguish between the direct and transitive dependencies. This seems like something that at least Bloop and `sbt-bloop` could...

(This is not a high prio thing at all - just wanted to share what I ran into before I forget)