-
Notifications
You must be signed in to change notification settings - Fork 18k
cmd/go: no Module information in list -e output after any error loading package #44287
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
In I don't think anything prevents us from populated the |
Hey @jayconrod , I would like to help out to fix this issue. How should I proceed? Thanks :) |
@sidntrivedi012 Your help is most welcome. I think this can be fixed in pkg.go by moving this block up to right after we push the import path on the stack. Please make sure to add a regression test in src/cmd/go/testdata/script. There's a README there that explains the format. |
I can take this one up if this in the backlog. @jayconrod Please feel free to assign this one to me. 🙏🏽 |
Hey @supriya-premkumar , I got somewhat stuck in the weekdays so couldn't get the bandwidth to work on it. I am planning to write a patch for it in this weekend. Will surely comment here to assign it to you if I fail to triage it. Thanks 😃 |
No worries at all. Go for it! |
The existing implementation ignores module info if there is any error loading the package. Fixes golang#44287
Change https://golang.org/cl/313549 mentions this issue: |
The existing implementation ignores module info if there is any error loading the package. Fixes golang#44287
The existing implementation ignores module info if there is any error loading the package. Fixes golang#44287
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?
What did you expect to see?
What did you see instead?
This has implications for users of
go list
, i.e.go/packages
.The text was updated successfully, but these errors were encountered: