Skip to content
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

Broken "cloud.google.com/go/compute/metadata" dependency #1551

Closed
dualBreath opened this issue Nov 10, 2023 · 2 comments
Closed

Broken "cloud.google.com/go/compute/metadata" dependency #1551

dualBreath opened this issue Nov 10, 2023 · 2 comments
Assignees

Comments

@dualBreath
Copy link
Contributor

Expected Behavior

go mod tidy works fine

Current Behavior

go mod tidy doesn't work if called twice

Failure Information (for bugs)

Looks like this dependency cause it cloud.google.com/go/compute/metadata

Steps to Reproduce

  1. go mod tidy
  2. go mod tidy
  3. an error appears

Context

cloud.google.com/go/compute/metadata

Failure Logs

user:my-sdk user$ go mod tidy
user:my-sdk user$ go mod tidy
github.com/networkservicemesh/sdk/pkg/tools/tracing imports
go.opentelemetry.io/contrib/instrumentation/google.golang.org/grpc/otelgrpc tested by
go.opentelemetry.io/contrib/instrumentation/google.golang.org/grpc/otelgrpc.test imports
google.golang.org/grpc/interop imports
golang.org/x/oauth2/google imports
cloud.google.com/go/compute/metadata: ambiguous import: found package cloud.google.com/go/compute/metadata in multiple modules:
cloud.google.com/go v0.34.0 (/Users/user/go/pkg/mod/cloud.google.com/go@v0.34.0/compute/metadata)
cloud.google.com/go/compute/metadata v0.2.3 (/Users/user/go/pkg/mod/cloud.google.com/go/compute/metadata@v0.2.3)

@dualBreath
Copy link
Contributor Author

I've found that using go v1.21.4 covers this case and the cloud.google.com/go/compute/metadata dependency will not be a problematic dependency.

Screenshot 2023-11-24 at 14 26 26

@dualBreath
Copy link
Contributor Author

Let's try updating the go version to 1.20.11 in the .github repository and see if that solves the problem

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Done
Development

No branches or pull requests

2 participants