bazel-contrib / bazel-contrib/rules_go

Auto-complete stopped working with VSCode

Open
#4,286 14 comments 0 reactions 0 assignees View on GitHub
Dominant language
Go
Stars
1.5k
Forks
760
Avg merge
1d 11h
Merged PRs (30d)
12

Description

Hi,

I recently enabled auto-complete with the [editor support](https://github.com/bazel-contrib/rules_go/wiki/Editor-setup), which has been working great (thanks!) - but it suddenly stopped working.

I thought it might have been related to a gopls update, but reverting did not fix it.

I tried to do some [debugging](https://go.googlesource.com/tools/+/refs/tags/gopls/v0.4.2-pre1/gopls/doc/troubleshooting.md#vs-code), and see errors like:

```
[Error - 11:30:47 AM] Request textDocument/inlayHint failed.
Message: getting file for InlayHint: stat /home/kyle/.cache/bazel/_bazel_kyle/d86f6415f278f3ee1100d1200456d325/execroot/_main/bazel-out/k8-fastbuild/bin/external/rules_go+/stdlib_/gocache/72/72059092b7ebcd47e2a2a153e7d3c12cafc4d261d4f86a01ff6fb147d04fc2b4-d: no such file or directory
Code: 0
```

I wasn't sure if this was a new error that was causing something to stop or not. When I go to the gocache directory, it is just empty.

I've also noticed the "Inline Suggestions" in the bottom right of VS code just always says loading,

I do see some examples of `textDocument/documentSymbol` working.

Any further debugging suggestions welcome.

Thanks!

Kyle

Contributor guide

Open the contributing guide

Research direction

Start with the editor support wiki and the linked gopls troubleshooting guidance, then inspect the reported textDocument/inlayHint error and the empty gocache path. Compare the working documentSymbol requests with the failing inline suggestions and determine the relevant failure boundary. Done means VS Code autocomplete and inline suggestions work again without the reported missing-file error.

Written by the indexing model from the issue text.

Assessment

Tech stack
go, vscode
Domain
developer-experience, tooling
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.