-
Notifications
You must be signed in to change notification settings - Fork 17.9k
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
cmd/go: list -m -json often missing .Origin #67363
Comments
Interestingly, |
@findleyr thanks! That's 80% of a workaround for me! Unfortunately, the VCS info doesn't appear to always be present in the proxy: https://proxy.golang.org/rsc.io/edit/@v/v1.0.0.info |
That VCS info is not always present is, I believe, a known limitation. (CC @suzmue to confirm). The decision was made to not reprocess older versions in the proxy--even ignoring compute resources, we can't guarantee that older versions still exist in at the origin. But for x/tools@latest, VCS info is present, and yet not returned by |
probably related #66077 (comment) |
MergeOrigin will work when m1 or m2 both not nil. But if one of it is nil. We should return other one which is not nil. Fixes golang#67363
MergeOrigin will work when m1 or m2 both not nil. But if one of it is nil. It should return other one which is not nil. Fixes golang#67363
Change https://go.dev/cl/588575 mentions this issue: |
Go version
go version go1.22.3 darwin/arm64
Output of
go env
in your module/workspace:Bug report
This is a regression. With Go 1.22.3:
Note that there is no Origin field.
With Go 1.21.10:
Given the conversation in #57051, it is clear that the intent is that the Origin field be present.
Relevant to #18387.
The text was updated successfully, but these errors were encountered: