cmd/go: go list
prints the wrong Origin
data for the version resolved from a non-semver query
#61423
Labels
GoCommand
cmd/go
modules
NeedsInvestigation
Someone must examine and confirm this is a valid issue and not a duplicate of an existing one.
Milestone
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?
A result with either a non-cacheable
Origin
(currently, an emptyHash
,TagSum
, andRepoSum
), or anOrigin
with aRef
matching the one we would need to re-resolve in the upstream repo.What did you see instead?
When a proxy is used, the result may include a cacheable
Origin
, as if the command had requested the fully-resolved version instead of a query:The text was updated successfully, but these errors were encountered: