scalacenter/bloop

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

megri

@megri

I'm running JDK 14+ and hitting this error: scalacenter/bloop#1384

Now, it seems this is fixed in snailgun 0.3.2, but bloop is still using version 0.3.1 from what I can see here https://github.com/scalacenter/bloop/blob/7e876299f2b1830775a2a4ee8fc219b4b167f1c4/project/Dependencies.scala#L55

Is there some other reason for not using the newer snailgun version?

Ricardo Gaspar

@ricardogaspar2

hey all! Maybe someone could help me here. I've been using Bloop with IntelliJ for a few months now and I'm very fond of it.
For quite some time have been having some difficulties with its interaction with SBT - it might not be due to it, just guessing.
The problem: when some dependencies are updated in SBT, I've to first reload SBT sbt clean evicted reload before Bloop can use the lastest dependencies. Is there a way for Bloop to trigger SBT to do this? I didn't found any command to trigger that. Most of the times I use clean and compile bloop clean compile <projectname> but no success on fetching the new configs.

Additionally, I've noticed that there's no reload command for Bloop. Does it do it automatically?

4 replies

Tomasz Godzik

@tgodzik

We've just released https://github.com/scalacenter/bloop/releases/tag/v1.4.5 - there was a small hickup with the release and I haven't yet managed to update the arch package to 1.4.5, I will try to fix that tomorrow. Unless anybody has access and could do it in the meantime.

Rohith Madamshetty

@rohithbittu33

i have my sbt env setup and i did my test run which ran successfully and when i am running my application i am getting the following error

  100.0% [##########] 94.2 MiB (23.7 MiB / s)
[info] Fetched artifacts of 
[warn] There may be incompatibilities among your library dependencies; run 'evicted' to see detailed eviction warnings.
[info] Compiling 5 Scala sources to /home/ubuntu/rest-api/target/scala-2.13/classes ...
https://repo1.maven.org/maven2/org/scala-sbt/compiler-bridge_2.13/1.3.1/compiler-bridge_2.13-1.3.1.pom
  100.0% [##########] 3.0 KiB (31.4 KiB / s)
https://repo1.maven.org/maven2/org/scala-sbt/util-interface/1.3.0/util-interface-1.3.0.jar
  100.0% [##########] 2.5 KiB (66.1 KiB / s)
[info] Non-compiled module 'compiler-bridge_2.13' for Scala 2.13.1. Compiling...
Killed

can anyone help me how to get rid of this
i am not able to execute the program

its getting killed when i run the program

i even tried changing the scala versions but it happens the same everytime

Tomasz Godzik

@tgodzik

@rohithbittu33 that looks like an sbt issues, could you ask in sbt/sbt channel ?

vito-c

@vito-c

does bloop always treat warnings as fatals or does it respect the scalacoptions? It keeps telling me that it

Compiled myproject (22960ms)
[E] Failed to compile 'myproject'

And then there a bunch of deprecation warnings. So I am thinking bloop is not respecting my scalacoptions?

Rohith Madamshetty

@rohithbittu33

@tgodzik thanks for the info

Adrian Legaspi

@akilegaspi

Hi everyone, I'm encountering a problem where bloop just get stuck and not giving any feedback after a project compiles.

Is there a way for me to debug this?

e.g.
Compiled projectN (128812ms)
then nothing else follows even though I'm expecting another project to compile

Adrian Legaspi

@akilegaspi

I noticed something extremely odd also.
using jvisualvm, I can see that once the compilation gets stuck, the thread count just starts increasing like crazy

Adrian Legaspi

@akilegaspi

what I get on zipkin is some io is being done (which clearly isn't because the build has been stuck for more than 45 mins already), if that helps

Tomasz Godzik

@tgodzik

@vito-c it should respect the scalacOptions and it doesn't treat warnings as fatals as default

Normally I get:

Compiling root (1 Scala source)
[W]  [E1] src/main/scala/Main.scala:40:5
[W]       A pure expression does nothing in statement position; you may be omitting necessary parentheses
[W]       L40:     "s"
[W]                ^
[W] src/main/scala/Main.scala: L40 [E1]
Compiled root (349ms)

@akilegaspi this might be a bug inside Bloop, do you have a reproduction available? Could you try maybe with the most recent Bloop 1.4.5?

Adrian Legaspi

@akilegaspi

@tgodzik I'm using the latest bloop, I'll try to get a reproduction of it.

but tbh I don't know how I would be able to reproduce it because it's quite sporadic, I somehow have solved it by giving bloop more ram

Tomasz Godzik

@tgodzik

it might have been a lot of GC then?

how much ram did you need to give it? @akilegaspi

Adrian Legaspi

@akilegaspi

I was thinking about that but I don't see anything happening on the CPU (as per the graph shows) during the time the compile has frozen

When the freeze happened, I gave it 4g, made it 6g to help the jvm further.

Tomasz Godzik

@tgodzik

That seems a lot, but it seems to have been used up fully. It might be some real issue or maybe the size of the project? Hard to say. What worries me more is the sudden explosion of threads at the end. An idea what threads are those?

1 reply

vito-c

@vito-c

@tgodzik I guess I'm confused why it says [E] Failed to compile 'myproject' at the end when it successfully compiles. I can also compile it in SBT just fine

Where communities thrive

People

Repo info

Activity