You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Error diagnostics aren't showing when using Bazel and Metals. This time though for Scala 2.12 (I see the other issue for Scala3 but I presume that's a separate issue).
Expected behavior
No response
Operating system
Linux
Editor/Extension
VS Code
Version of Metals
v1.2.2
Extra context or search terms
See this in the metals.log:
2024.04.05 23:53:46 INFO INFO: Found 1 target...�[0m
2024.04.05 23:53:46 INFO checking cached actions�[0m
2024.04.05 23:53:46 INFO [0 / 2] [Prepa] BazelWorkspaceStatusAction stable-status.txt�[0m
2024.04.05 23:53:46 INFO [1 / 2] scala @//.../netflix/aeviz/service:service; 0s remote-cache, worker�[0m
2024.04.05 23:53:47 INFO ERROR: /home/coder/rankresearchv2/aeviz/src/main/scala/com/netflix/aeviz/service/BUILD.bazel:10:14: scala @//aeviz/src/main/scala/com/netflix/aeviz/service:service failed: (Exit 1): scalac failed: error executing command (from target //aeviz/src/main/scala/com/netflix/aeviz/service:service) bazel-out/k8-opt-exec-2B5CBBC6/bin/external/io_bazel_rules_scala/src/java/io/bazel/rulesscala/scalac/scalac '--jvm_flag=-DNetflixInvalidateCacheArg=20220508' '--jvm_flag=-Xss2m' '--jvm_flag=-Xmx2g' ... (remaining 1 argument skipped)�[0m
2024.04.05 23:53:47 INFO aeviz/src/main/scala/com/netflix/aeviz/service/RankService.scala:49: error: not found: value asfd�[0m
2024.04.05 23:53:47 INFO asfd�[0m
2024.04.05 23:53:47 INFO ^�[0m
2024.04.05 23:53:47 INFO aeviz/src/main/scala/com/netflix/aeviz/service/RankService.scala:87: warning: local val seed in method applyOrElse is never used�[0m
2024.04.05 23:53:47 INFO val seed = s.getOrElse(defaultSeed)�[0m
2024.04.05 23:53:47 INFO ^�[0m
2024.04.05 23:53:47 INFO aeviz/src/main/scala/com/netflix/aeviz/service/RankService.scala:113: warning: local val seed in method applyOrElse is never used�[0m
2024.04.05 23:53:47 INFO val seed = s.getOrElse(defaultSeed)�[0m
2024.04.05 23:53:47 INFO ^�[0m
2024.04.05 23:53:47 INFO aeviz/src/main/scala/com/netflix/aeviz/service/RankService.scala:134: warning: local val seed in method applyOrElse is never used�[0m
2024.04.05 23:53:47 INFO val seed = s.getOrElse(defaultSeed)�[0m
2024.04.05 23:53:47 INFO ^�[0m
2024.04.05 23:53:47 INFO three warnings found�[0m
2024.04.05 23:53:47 INFO one error found�[0m
2024.04.05 23:53:47 INFO Build failed�[0m
2024.04.05 23:53:47 INFO java.lang.RuntimeException: Build failed�[0m
2024.04.05 23:53:47 INFO at io.bazel.rulesscala.scalac.ScalacInvoker.invokeCompiler(ScalacInvoker.java:53)�[0m
2024.04.05 23:53:47 INFO at io.bazel.rulesscala.scalac.ScalacWorker.compileScalaSources(ScalacWorker.java:253)�[0m
2024.04.05 23:53:47 INFO at io.bazel.rulesscala.scalac.ScalacWorker.work(ScalacWorker.java:69)�[0m
2024.04.05 23:53:47 INFO at io.bazel.rulesscala.worker.Worker.persistentWorkerMain(Worker.java:86)�[0m
2024.04.05 23:53:47 INFO at io.bazel.rulesscala.worker.Worker.workerMain(Worker.java:39)�[0m
2024.04.05 23:53:47 INFO at io.bazel.rulesscala.scalac.ScalacWorker.main(ScalacWorker.java:33)�[0m
The text was updated successfully, but these errors were encountered:
aishfenton
changed the title
Missing error eiagnostics using Bazel (for Scala 2.x)
Missing error diagnostics using Bazel (for Scala 2.x)
Apr 6, 2024
Hmm... does this happen for you on some sample Bazel repos or only in yours? Are you able to provide the versions of Bazel rules-scala and bazel-bsp versions you are using?
We're using Scala 2.12.18, Bazel 6.3.2, rules_scala 6.4.0 and nightly build of Metals 1.2.2+99-c0e45169-SNAPSHOT (can update to a newer nightly if that helps?)
Describe the bug
Error diagnostics aren't showing when using Bazel and Metals. This time though for Scala 2.12 (I see the other issue for Scala3 but I presume that's a separate issue).
Expected behavior
No response
Operating system
Linux
Editor/Extension
VS Code
Version of Metals
v1.2.2
Extra context or search terms
See this in the
metals.log
:The text was updated successfully, but these errors were encountered: