Open yashLadha opened 3 years ago
Thanks for the reporting! The semanticdb files needed for the navigation are produced during the compilation. Did the compilation at any point finish successfully? I see there is a warning about the annotations, did it stop the entire project from being compiled? I am not sure if annotation processor is supported properly in Bloop currently.
Yes compilation is completed successfully and jump to definition works for some files as well.
So this might ba an issue with annotation processor https://github.com/scalacenter/bloop/issues/962 :thinking:
This will need to be fixed upstream in Bloop and currently compilation will most likely not finish successfully.
@tgodzik I see that the linked issue is merged it latest version of metals released with these changes?
@yashLadha that was the plan! However, we will need to do a Bloop release also, so not sure timewise if that will come before the bloop release. In case it's later you should be able to just update the Bloop version in Metals
@yashLadha you can try out a new Bloop version 1.4.6-33-1c6f6712
in the Metals: Bloop Version
settings. I want to confirm some things first before doing a proper release.
Checked it out myself and it seems we are getting:
2021.01.28 15:54:18 WARN No processor claimed any of these annotations: org.apache.kafka.common.annotation.InterfaceStability.Unstable,java.lang.FunctionalInterface,org.apache.kafka.common.annotation.InterfaceStability.Evolving,java.lang.SafeVarargs
not sure how to handle that in Bloop :/
same thing happend
WARN No processor claimed any of these annotations: org.apache.kafka.common.annotation.InterfaceStability.Unstable,org.apache.kafka.common.annotation.InterfaceStability.Evolving,java.lang.SafeVarargs
why is this removed from v1.0.0 milestone ?
This still happens randomly. There are no compilation errors at all.
i have the same issue, very big project. compiles fine. but in some files code navigation just doesn't work.
Have the same issues, output log in vs code prints that compilation has finished, but on some files navigation simply doesn't work with exact same problem
if someone uses Scala 2.13.9, see https://github.com/scalameta/metals/issues/4449 workaround: revert to 2.13.8 / use the latest SNAPSHOT of Metals / wait for the next Metals release (it's around the corner!)
Also, when you hit the same issue, please attach your
That information is really helpful for fixing this issue.
what kind of symbol you tried to navigate is important, for example, code navigation doesn't work for mutable
in
val x: collection.mutable.Map[String, Int] = ???
(it might navigate to the package object if exists. maybe we should go somewhere anyway 🤔 ). With this information, we can make things better.
This issue has two perspectives.
It sounds like a SemanticDB issue (because we see the log saying Code navigation doesn't work because ... SemanticDB file doesn't exist ...
), but it's a kind of presentation compiler's code navigation issue.
We might want to add some more words to the log like "falling back to the compiler-based code navigation..." because the current log message seems a bit confusing.
Describe the bug
When opening kafka project in neovim with metals, when trying to go for the definition of module it is saying that the semantic db file doesn't exist so we cannot use the go-to definition in the file.
To Reproduce
Steps to reproduce the behavior:
AdminZkClient.scala
fileRackAwareMode
and try to go to definitionExpected behavior
Ideally, it should go to the definition of that file. Is there something I am missing?
Screenshots
Installation:
Additional context
Search terms