Skip to content
This repository has been archived by the owner on Jul 15, 2023. It is now read-only.

"Find All References" shows no result but "Peek References" shows correct results. #2197

Closed
krasoffski opened this issue Dec 19, 2018 · 6 comments
Labels

Comments

@krasoffski
Copy link

krasoffski commented Dec 19, 2018

Environment:

  • OS: Xubuntu 18.04.1 LTS
  • vscode: 1.30.1, dea8705087adb1b5e5ae1d9123278e178656186a, x64

Steps to Reproduce:

  1. Open big go project.
  2. Select function and use Right Mouse Click choose "Find All References" - NO RESULT
  3. Select "Peek References" - all results provided.

Addition info:
After some amount time or after using "Peek References" "Find All References" shows correct result but then might fail.

Trace logs does not show correct info about root cause, only error like: ERR An unknown error occurred. Please consult the log for more details. (I use -v with --debug=trace).
image
"Peek References" always works correctly but "Find All References" fails about 70% of cases.

This might be important, that adding following error too:

[Extension Host] Command failed: /opt/go/bin/go doc -c -cmd -u repo/module resolutionID
doc: no symbol resolutionID in package repo/module exit status 1
@krasoffski
Copy link
Author

It seems like problem might be related following behavior:

  • When you put pointer to function name and and choose "Find All References" it works w/o problem.
  • When you select function name and choose "Find All References" it does not work with issue unknown error

@saibing
Copy link

saibing commented Dec 28, 2018

@saibing
Copy link

saibing commented Dec 30, 2018

@krasoffski
It's may be a go language server's bug. bingo have already fixed this bug.

you can try it.

@ramya-rao-a
Copy link
Contributor

ramya-rao-a commented Dec 30, 2018

@krasoffski Thanks for reporting!

@saibing This is happening because VS Code is passing different positions for the 2 operations. See
microsoft/vscode#65127 (comment)

Let's wait and see if we can get an upstream fix for this.

@krasoffski
Copy link
Author

krasoffski commented Apr 9, 2019

Seems like this issue can be closed. Does anyone still have this problem?

@ramya-rao-a
Copy link
Contributor

I was not aware of any upstream fixes here, but if you don't see this problem anymore, I'll go ahead and close this issue

@vscodebot vscodebot bot locked and limited conversation to collaborators Jun 20, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

3 participants