Chris Kipp

In case anyone here missed it and is following along, [v1.8.0-RC1 was realeased](https://github.com/sbt/sbt/releases/tag/v1.8.0-RC1) which does bring in the 2.x version of scala-xml. Please do test it out and report back...

> Notice also that sbt does respond with an error but Metals does not forward it to the user: huh indeed. Looking if that compile request fails it looks like...

Alright so I dug into this a little bit. My first reaction was to make some code changes [here](https://github.com/scalameta/metals/blob/1db3cf9dc3f1e2388eb5572f9de5e70fd4cf245f/metals/src/main/scala/scala/meta/internal/metals/Compilations.scala#L225-L240) in Metals since we don't actually capture any failures here. However...

Taken from https://github.com/sbt/sbt/issues/6914 > I kind of agree. Here's the issue I created in 2017 - https://github.com/sbt/sbt/issues/3681 > Likely we can't do much in sbt 1.x, but we can hope...

> non-VSCode legacy clients 😉 whoa whoa whoa 😄

Thanks for the extra info @fiatjaf. I'll need to dig in a bit further, but upon first try I just open a random scala file in the build and the...

I'm transferring this over to the main repo. I tried importing this build via VS Code and also get the same issues, so it's not something specific to `nvim-metals`. Just...

@Arthurm1 teach me obi wan, how did you get that info? I ran with `--info` and I get close, `--trace` gave me more, but still not what I wanted. I...

> @ckipp01 I often use the `--stacktrace` option e.g. `./gradlew bloopInstall --stacktrace` to get the detail but I didn't need it here. Super, thanks for the detailed explanation!

> Indeed, there are no unit tests yet, I'm doing manual tests for the moment, but I'm starting to look at how to write a test suite, I might need...