Skip to content
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

Error loading workspace #1064

Closed
Kurt-Shiwz opened this issue Dec 28, 2020 · 3 comments
Closed

Error loading workspace #1064

Kurt-Shiwz opened this issue Dec 28, 2020 · 3 comments
Labels
FrozenDueToAge WaitingForInfo Issue is not actionable because of missing required information, which needs to be provided.

Comments

@Kurt-Shiwz
Copy link

os: macos 11.1 (20C69)
vscode:1.52.1
go: go version go1.15.6 darwin/amd64

when i pull the lastest version(go.mod change), the error loading always running until i run "rm -rf vendor && go mod vendor".
i know it is't a real bug, because i use vendor(i like to see the pkg files in left explore, go mod can just see the single file),
i want to know if where is a setting can disable try to load when the error happened. as i see it running until i fix it.

Error loading workspace: go [-e -json -compiled=true -test=true -export=false -deps=true -find=false -- builtin
@stamblerre
Copy link
Contributor

@Kurt-Shiwz: Can you please share the full text of the error? Based on what you're saying about vendoring, it sounds like you may have an issue with inconsistent vendoring. In that case, you should also see a diagnostic with a suggested fix--do you see a diagnostic on the go.mod file?

@stamblerre stamblerre added the WaitingForInfo Issue is not actionable because of missing required information, which needs to be provided. label Dec 28, 2020
@Kurt-Shiwz
Copy link
Author

@Kurt-Shiwz: Can you please share the full text of the error? Based on what you're saying about vendoring, it sounds like you may have an issue with inconsistent vendoring. In that case, you should also see a diagnostic with a suggested fix--do you see a diagnostic on the go.mod file?

it seem like pkg version in go.mod new than vendor/ **, so i "rm -rf vendor" and run "go mod vendor" use the newest pkg, after that it ok

@stamblerre
Copy link
Contributor

That sounds like inconsistent vendoring, and you should see the diagnostic with the quick fix. You can just click the suggested fix to resolve the problem. Unfortunately, inconsistent vendoring is a critical problem for the go command, so until golang/go#39164 is resolved, there's nothing else that can be done.

@golang golang locked and limited conversation to collaborators Dec 28, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
FrozenDueToAge WaitingForInfo Issue is not actionable because of missing required information, which needs to be provided.
Projects
None yet
Development

No branches or pull requests

3 participants