Bloop CLI fails (again/still?) with Uninitialized TermDisplay

[jypma]

Issue #2840, although earlier fixed by #2841, seems to still occur for me. Strangely, I only see it on one of my machines (which as similarly configured).

• Bloop 2.0.19
• JDKs 21.0.10+7 and 26.0.2 (although bloop seems to be a native image, so that might not be relevant)

I've tried both Bloop as built from the AUR, as well as manually downloaded through coursier, with the same result:

$ bloop compile main
Exception in thread "main" java.lang.Exception: java.lang.Exception: Uninitialized TermDisplay coursier.cache.loggers.RefreshLogger@3a8578c1
	at bloop.cli.options.DefaultOptions$.$anonfun$bloopRifleConfig$13(DefaultOptions.scala:137)
	at coursier.cache.CacheLogger.use(CacheLogger.scala:51)
	at coursier.cache.CacheLogger.use$(CacheLogger.scala:49)
	at coursier.cache.loggers.RefreshLogger.use(RefreshLogger.scala:223)
	at bloop.cli.options.DefaultOptions$.downloadJvm$1(DefaultOptions.scala:135)
	at bloop.cli.options.DefaultOptions$.defaultJvmCmd$lzycompute$1(DefaultOptions.scala:147)
	at bloop.cli.options.DefaultOptions$.defaultJvmCmd$1(DefaultOptions.scala:146)
	at bloop.cli.options.DefaultOptions$.$anonfun$bloopRifleConfig$17(DefaultOptions.scala:157)
	at scala.Option.getOrElse(Option.scala:201)
	at bloop.cli.options.DefaultOptions$.bloopRifleConfig(DefaultOptions.scala:157)
	at bloop.cli.options.DefaultOptions.bloopRifleConfig(DefaultOptions.scala:44)
	at bloop.cli.Default$.run(Default.scala:25)
	at bloop.cli.Default$.run(Default.scala:18)
	at caseapp.core.app.CaseApp.main(CaseApp.scala:178)
	at caseapp.core.app.CommandsEntryPoint.main(CommandsEntryPoint.scala:370)
	at bloop.cli.Bloop.main(Bloop.scala)
Caused by: java.lang.Exception: Uninitialized TermDisplay coursier.cache.loggers.RefreshLogger@3a8578c1
	at coursier.cache.loggers.RefreshLogger.$anonfun$updateRunnable$2(RefreshLogger.scala:257)
	at scala.Option.getOrElse(Option.scala:201)
	at coursier.cache.loggers.RefreshLogger.updateRunnable(RefreshLogger.scala:257)
	at coursier.cache.loggers.RefreshLogger.checkInitialized(RefreshLogger.scala:310)
	at coursier.cache.FileCache.$anonfun$ensureLoggerIsInitialized$1(FileCache.scala:409)
	at coursier.util.Task$.wrap(Task.scala:82)
	at coursier.util.Task$.$anonfun$delay$2(Task.scala:47)
	at scala.concurrent.Future$.$anonfun$apply$1(Future.scala:691)
	at scala.concurrent.impl.Promise$Transformation.run(Promise.scala:500)
	at java.base@17.0.5/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136)
	at java.base@17.0.5/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635)
	at java.base@17.0.5/java.lang.Thread.run(Thread.java:833)
	at org.graalvm.nativeimage.builder/com.oracle.svm.core.thread.PlatformThreads.threadStartRoutine(PlatformThreads.java:775)
	at org.graalvm.nativeimage.builder/com.oracle.svm.core.posix.thread.PosixPlatformThreads.pthreadStartRoutine(PosixPlatformThreads.java:203)

[tgodzik]

Thanks for reporting! Not sure how this could be still happening. Are you sure that the correct version of Bloop is running? You can check it with bloop about

[jypma]

Thanks for checking! Yeah, so bloop about yields the same exception :P

Pacman reports bloop 2.0.19-1, which was installed through yay. I've also tried installing it with makepkg directly from the AUR's repo, with no difference. The stacktrace does also seem to line up with the latest source, fwiw. I do agree though, this should not be happening... I'll poke at it a bit more myself, to see it something comes up.