Chris Kipp

> I don't think that it's a Metals issue. Sure, but as a user when you use a Metals feature and it breaks your build, they see it as a...

Thanks for reporting this @caenrique! You're correct, this shouldn't happen. I'd expect the user to see a nicer message this this, not an `Internal error` message. We need to handle...

Yea I'm sort of liking `iii` since it would most closely align with the behavior of triggering scalafmt for the first time. The only tricky this is that if we...

> I understand it would reduce the complexity of the ScalafixProvider here, but how would it help in that particular issue? Sure, to expand on the example I had, let's...

It's been there for a while, as I've come across this quite a bit in the past, but never created an issue for it. As for where the actual is...

Thanks for the report @frioux. Just to tie these all together (and for visibility, let's continue the conversation here, not on Discord), I hit on the same issue that @dos65...

Alright, more issues. After doing the steps I still wasn't able to do a bloop install. ``` 2022.06.02 15:06:13 ERROR 2022.06.02 15:06:13 INFO See https://docs.gradle.org/7.2/userguide/command_line_interface.html#sec:command_line_warnings 2022.06.02 15:06:13 ERROR * What...

🤔 weird after running `./gradlew build , to see it working?` I was able to get it to compile, and then looking at the `classpath` entry in the `.bloop/spark-example.json` I...

> but I imagine the reason bloop compiles is because you've already created the jar using gradle Exactly this. This is why when I first tried I had compilation issues...

Following up from the convo we were having on the scalameta discord, this looks to be the issue mentioned in https://github.com/coursier/coursier/issues/2395 although we should probably leave this issue open since...