Go To Definition and Go To Implementation not working properly

[vzmerr]

Describe the bug

In the following code in Scala 3 Completions file, we have the following problem on the toString method of Symbol.Symbol

https://user-images.githubusercontent.com/109077949/181247893-630530b5-cd5a-422b-9e01-901cf76ddb93.mov

:

Expected behavior

No response

Operating system

macOS

Editor/Extension

VS Code

Version of Metals

0.11.7+61-a6299f3a-SNAPSHOT

Extra context or search terms

No response

[tgodzik]

Looks like it's the same issue as was fixed in https://github.com/lampepfl/dotty/pull/15536

We can confirm when we update metals to 3.2.0

[vzmerr]

One extra case to check

[tgodzik]

One extra case to check

That is unrelated, but it does work for me. It needs the code to compile though.

[vzmerr]

One extra case to check

That is unrelated, but it does work for me. It needs the code to compile though.

I ran the tests, so it is compiled. I wonder why it is not working on my side.

By the way, I guess it would be cool if we add a trouble shoot tutorial in the docs.

[tgodzik]

I ran the tests, so it is compiled. I wonder why it is not working on my side.

Where did you run the tests though? IF from test explorer then it can't work without semanticdb, which seems to be the case here

[vzmerr]

Where did you run the tests though?

sbt

[tgodzik]

Where did you run the tests though?

sbt

Yeah, sbt compilation is unrelated unless you use sbt server. If you use Bloop it probably didn't compile. Maybe something is shown in the problems view?

[vzmerr]

Yes, 66 problems

[vzmerr]

the problem might be Bloop

[tgodzik]

Try Clean compiler workspace command

[vzmerr]

Try Clean compiler workspace command

after running sbt clean followed by sbt compile, the problems number increased to 227.

Same with Clean Java Language Server Workspace command.

[dos65]

@vzmerr this clean command is located in Metals ta

[kpodsiad]

@vzmerr if you are using sbt extensively you may consider switching build server to sbt

[vzmerr]

@dos65 thanks the problems got reduced to 3

@kpodsiad

if you are using sbt extensively you may consider switching build server to sbt

how do I do that?

[vzmerr]

The standard way of using Metals is with Bloop, though. So I guess for the sake of revealing the functionality of Metals from the user perspective, I have to stick to Bloop.

[dos65]

@vzmerr you need to trigger compilation once from sbt - BuildInfo is a generated source and only sbt can generate it

[vzmerr]

@vzmerr you need to trigger compilation once from sbt - BuildInfo is a generated source and only sbt can generate it

But I did so. I ran the test.

[vzmerr]

I think I really have to make a troubleshoot doc PR

[vzmerr]

The issue got solved by deleting the .bloop directory and then compiling and importing build. credit to @dos65 Also, with the newest work of Vadim on Bloop, this issue might not be encountered by users again :)

[vzmerr]

The issue got solved by deleting the .bloop directory and then compiling and importing build. credit to @dos65 Also, with the newest work of Vadim on Bloop, this issue might not be encountered by users again :)

I mean the Problems view issue, not the javadoc on hover one.

[tanishiking]

Now Scala 3.2.0 is released https://github.com/lampepfl/dotty/pull/15536 closing, if there're remained issues related to this, feel free to open a new one :)