-
Notifications
You must be signed in to change notification settings - Fork 18k
x/tools/gopls: Error due to trying to respect transient replace #44622
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Do you have A repro would also be helpful. If you're working on github.com/openshift/ci-tools, I tried opening that project and it seemed to go fine with default gopls settings. |
@heschik doesn't happen on master, but here: openshift/ci-tools@c50dc4e I don't have any special settings. I do not use vscode but vim-go/coc.nvim:
Logs:
The error are in the second log towards the end |
Thanks for the logs. It appears that when you jumped to definition on a type in the
At that point I think |
It appears this is vim-go. I didn't intend to use the vim-go lsp integration in the first place, I only have it for the highlighting and coc-nvim for the lsp integration. The latter doesn't have any issues with this. Thanks a lot for your help! |
What version of Go are you using (
go version
)?Does this issue reproduce with the latest release?
yes
What operating system and processor architecture are you using (
go env
)?go env
OutputWhat did you do?
I have a go project that imports "github.com/hashicorp/vault/api". That module in turn depends on github.com/hashicorp/vault/sdk but replaces it:
github.com/hashicorp/vault/sdk => ../sdk
This seems to break the gopls completion, it throws errors like this:
To my understanding, a
replace
should never get propagated. In this case it appears that happens for gopls, because my own project does not have thisreplace
:Project building and testing works fine, so this issue appears to be specific to
gopls
What did you expect to see?
gopls
to ignore the transient replace directive and not throwing an error when accessing objects in thereWhat did you see instead?
The text was updated successfully, but these errors were encountered: