You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Tried to upgrade package using go get github.com/prometheus/prometheus@master
What did you expect to see?
go get to not consider the unit test files of the dependency for fetching transitive dependencies.
What did you see instead?
go get fetching transitive dependencies for unit tests while at the end the unit test files are never vendored.
Sometimes those unit test dependencies have tendancy to cause issues like this
go: finding module for package k8s.io/api/settings/v1alpha1
github.com/cortexproject/cortex/pkg/api imports
github.com/prometheus/prometheus/config tested by
github.com/prometheus/prometheus/config.test imports # <-- the culprit
github.com/prometheus/prometheus/discovery/kubernetes imports
k8s.io/client-go/kubernetes imports
k8s.io/client-go/kubernetes/typed/settings/v1alpha1 imports
k8s.io/api/settings/v1alpha1: module k8s.io/api@latest found (v0.20.2), but does not contain package k8s.io/api/settings/v1alpha1
The text was updated successfully, but these errors were encountered:
Closing this since it looks like we have some use case. But ideally would have seen those individual use cases (like go test all) to check and fetch transitive test dependencies on-demand instead of always. replace directives to the rescue for now.
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?
Tried to upgrade package using
go get github.com/prometheus/prometheus@master
What did you expect to see?
go get
to not consider the unit test files of the dependency for fetching transitive dependencies.What did you see instead?
go get
fetching transitive dependencies for unit tests while at the end the unit test files are never vendored.Sometimes those unit test dependencies have tendancy to cause issues like this
The text was updated successfully, but these errors were encountered: