-
Notifications
You must be signed in to change notification settings - Fork 17.8k
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
gopls/internal/analysis: noresultvalues diagnostic triggers "end > end of file + 1" bug (via telemetry) #68105
Labels
gopls/telemetry-wins
gopls
Issues related to the Go language server, gopls.
NeedsInvestigation
Someone must examine and confirm this is a valid issue and not a duplicate of an existing one.
Tools
This label describes issues relating to any tools in the x/tools repository.
Milestone
Comments
This stack
|
This is probably a bit gnarly to track down, though surely it's a go/parser bug. Bumping to v0.18, when hopefully we can fix go/parser. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
gopls/telemetry-wins
gopls
Issues related to the Go language server, gopls.
NeedsInvestigation
Someone must examine and confirm this is a valid issue and not a duplicate of an existing one.
Tools
This label describes issues relating to any tools in the x/tools repository.
This stack
lMZltw
was reported by telemetry:noresultvalues reports a diagnostic with an End position well beyond EOF:
The file was not "fixed", i.e. it is unmodified parser output.
Issue created by golang.org/x/tools/gopls/internal/telemetry/cmd/stacks.
Dups: PFz3wQ uU3LXw s5dvOQ v7eTGw
The text was updated successfully, but these errors were encountered: