scalacenter/bloop

Adam Rosien

@arosien

if i add scalaVersion := "2.13.2" to my top-level build.sbt i get the same issue.

i have ThisBuild / scalaVersion := "2.13.2" already there

Eric K Richardson

@ekrich

Yes the build thing is the sbt file. That is annoying, maybe the Metals folks could relax that warning for sbt.

I work on Scala Native which is always 2.11.12 so I get another annoying message too.

Are you sticking with 1.2.8 for ivy vs cousier?

Adam Rosien

@arosien

no, that's just the version i set whenever i started my project and i try to never ever touch the build after that

Eric K Richardson

@ekrich

ok, but upgrading sbt to 1.3.13 is pretty safe and you get lots of improvements.

Adam Rosien

@arosien

i don't really use sbt, i use bloop, but i'll update if it helps

oh nice, it fixes my issue since that version of sbt uses scala 2.12.10, which is supported by metals

yay!

:clap: @ekrich

Eric K Richardson

@ekrich

Super, glad I could help.

m4dc4p

@m4dc4p

I use metals from VS code (and thus am using bloop). I also use sbt to run tests. When I save files in VS code, bloop will compile my project. When I run tests in sbt, sbt also compiles my project. Can I make sbt use the build artifacts produced by bloop, or can bloop run my tests (preferably from sbt)?

Krzysiek Bochenek

@kpbochenek

@m4dc4p bloop can run your tests! sbt might not be used at all in that case and you only compile your code with bloop

m4dc4p

@m4dc4p

@kpbochenek Oh! Would I use the bloop CLI to do that? (metals has no support for running tests AFAIK)

Krzysiek Bochenek

@kpbochenek

It has but let's focus on CLI, I do that e.g. in scalameta project:
bloop test testsJVM -o scala.meta.tests.parsers.VarargParameterSuite

and benefit of that is that bloop most likely already compiled your code so it will run instantly :)

m4dc4p @m4dc4p starts installing the bloop CLI

m4dc4p

@m4dc4p

Fantastic, thank you!

Chris Kipp

@ckipp01

I'm a big fan of the bloop cli. If it helps, I have some more examples on here https://chris-kipp.io/blog/a-bloop-tour-for-metals-users

m4dc4p

@m4dc4p

@ckipp01 cool thank you!

m4dc4p

@m4dc4p

WEll coursier failed to install bloop for me (some SSL problem :() but I was able to download the bloop binary & got that working. Quite nice!!!

m4dc4p

@m4dc4p

Any idea why bloop would loose track of a directory under bloop-bsp-clients-classes? I'm getting errors running bloop compile where it complains that a file is not found:

C:\Users\Justin\Source\xxx\bloop\db\bloop-bsp-clients-classes\classes-Metals-hFsrTRk0QjCJiRjDo1RBzQ==\com\xxx\dashboard\db\SignatureQueries$anon$generic$macro$110$1.class

And it turns out "classes-Metals-hFsrTRk0QjCJiRjDo1RBzQ==" does not exist. I'm running metals in VS Code and the bloop CLI at the same time, if that makes a difference.

m4dc4p

@m4dc4p

Killing the java process made the problem go away

Eric Peters

@er1c

I noticed https://virtuslab.com/case-study/improving-compilation-speed-by-order-of-magnitude/ post recently, are any of these "cache" features just leveraging something from bloop (that others could enjoy)?

vonchav

@voonchav_gitlab

Hi all, I'm having problem compiling my integration test with bloop. I have no problem with sbt. I share test fixtures between unit tests and integration tests. I have this in my build.sbt for enabling the share:

 .settings(
    dependencyClasspath in IntegrationTest :=
     (dependencyClasspath in IntegrationTest).value ++ (exportedProducts in Test).value
  )

I'm a noob with bloop and I used sbt bloopInstall to generate the bloop projects. I wonder maybe the sharing is a special case and requires some customization in the bloop projects. Please advise. Thanks.

Corey O'Connor

@coreyoconnor

I have a project that with code like:

dependsOn(
anotherProject % "optional->compile"
)

These dependencies are missing from the generated (sbt bloopInstall) bloop configurations. I tried adding this using the inConfig(Optional)(bloopSettings) pattern. Which did not work: The optional config has no productDirectories. From a developer perspective, I'd expect these to be treated like compile dependencies. Which, assuming correct so far, requires changing: https://github.com/scalacenter/bloop/blob/a35149836cfebcd6041f84fc17a2a2b896dbcb33/integrations/sbt-bloop/src/main/scala/bloop/integrations/sbt/SbtBloop.scala#L505

Does that sound correct? I'll file a ticket if so

Doron Somech

@somdoron

I'm using IntelliJ with bloop with "build on save" enabled, any way to disable IntelliJ to go to error if such exist? It is annoying writing some code, saving and going to another file

nafg

@nafg

yeah there's a setting somewhere

Jesse Atkinson

@jsatk

I keep getting this error when i try to run bloop tests but not in sbt tests. java.lang.ExceptionInInitializerError:

Anyone have any ideas why my tests would run fine in sbt but not bloop?

nafg

@nafg

@somdoron I think it's in Settings > Build, Execution, Deployment > Compiler > Automatically show first error in editor

mandeburka

@mandeburka

Hey. I'm looking into BloopBspServices.startDebugSession
I'm curios why DebugSessionParams.data field is treated as List[String] and not ScalaTestParams when dataKind == scala-test-suites?
It looks like metals follows this pattern to be compatible with bloop.
Is it compatible with BSP definition for running tests?

Doron Somech

@somdoron

@nafg thanks!

Will Sargent

@wsargent

I'm importing bloop 1.4.4 with Scala 2020.2.3 and running into "Problem executing BSP job"

1 reply

it keeps trying to reimport it

could be related to https://youtrack.jetbrains.com/issue/SCL-17821 but it's more recent than that

Pär Wenåker

@parwen68

I have "bloopInstalled" a rather big gradle project with 50+ modules. I then create a bsp project in Intellij and run into a long Intellij-indexining. The project has target folders that are excluded by default when importing a Gradle project in Intellij, but they are not excluded in in the BSP project. It is tedious to manually exclude all folders that should not be indexed. I guess that this is an issue with Intellij, but could it be solved by Bloop or the Gradle-plugin.

Ólafur Páll Geirsson

@olafurpg

@parwen68 this sounds like an IntelliJ issue, might be worth reporting to YouTrack

cc/ @jastice

Pär Wenåker

@parwen68

@olafurpg Thanks!

vito-c

@vito-c

how do I shut down bloop servers that are running? I tried kill -9 but they keep popping up

Chris Kipp

@ckipp01

you should be able to just do a bloop exit

vito-c

@vito-c

oh nice it wasn't on this list :D Available commands: about, autocomplete, bsp, clean, compile, configure, console, help, link, projects, run, testthat seemed to stop one of them but two java processors are still restarting with scala.meta.metals.Main at the end

Chris Kipp

@ckipp01

gotcha, then in that case, it's Metals that keeps restarting on you, which then starts Bloop

vito-c

@vito-c

ah ok should I take this to metals chat then? looks like a zombie node server?

Tomasz Godzik

@tgodzik

@vito-c bloop ng-stop

or if exit works then that might be fine

but yeah, Metals will automatically start a new one

Where communities thrive

People

Repo info

Activity