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
x/tools/gopls: errors in std lib files #32482
Comments
I’m sorry to hear you are encountering some issues. Would you be able to supply the logs and other diagnostic information suggested in the troubleshooting section here: |
@RobGraham: Can you try syncing to the latest version of |
@thepudds when i see the issue again i'll try grabbing the logs as it occurs. @stamblerre That link doesn't work. How do i know what version of gopls i'm using? I'm asking out of general curiosity but also because i've been actively updating gopls probably once or twice a week because of how unstable it is hoping these behaviors would be fixed. If i know how to compare my version with what you're referring to then i could better tell if the version I'm running includes the supposed fix. |
I think that link might have been missing an To you get the latest version of gopls, you would run:
|
Thank you for the correct link. And yes, i'm familiar with how to update and have done so probably twice since the 3rd which appears to be the commit date for that change. I've been primarily using the built in |
recent versions of gopls write their version information to the log. |
I previously tried seeing if i could execute gopls in terminal but get Update: It would help if i used my brain and remembered gopls is installed as a dependency in
|
That error message has been updated in recent commits, so I would recommend updating your |
@RobGraham: Are you still encountering this issue on the latest version of |
@stamblerre sorry for the tardiness. Spending the time to actually stop work, sift through the logs and report back when I just need to get on hasn't been a priority for me when i can just close and reopen vs code. However our team is still experiencing annoying behaviors. While I don't have the exact use case to report on right now, another one that plagues us a lot is when we create a new go file and add the appropriate package declaration at the top of the file and it complains after saving that
|
I will also try to do a better job giving you guys the info you need to actually fix the bugs so our sanity is not in jeopardy. |
Thank you for sharing the logs. Can you share the output of |
Sorry, i actually conducted an update prior to replying to the thread so i won't be able to give you any insight into the version if it was at all different to latest. But i'll definitely keep an eye out for the original issue and if i don't see any evidence of it within the week, we should be able to close this issue. Thanks again |
Hey @stamblerre not sure if this is helpful or in anyway related but I was conducting a |
|
Going to close this issue since it's been about a month since the last discussion. Please open a new issue if this problem persists. |
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?
Casually programming my application. No patterns that I've been able to discover.
What did you expect to see?
gopls to only error on legitimate issues within my workspace
What did you see instead?
gopls will occasionally throw errors outside of my project. It seems to be scanning std lib dir files. The behavior seems completely random and it acts like so many other errors thrown by gopls within my workspace that aren't actual errors. Closing and reopening vs code window always resolves the problems until the next occurrence.
The text was updated successfully, but these errors were encountered: