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

Incorrect version in sdk/metric go.mod #3215

Closed
MadVikingGod opened this issue Sep 21, 2022 · 1 comment · Fixed by #3216
Closed

Incorrect version in sdk/metric go.mod #3215

MadVikingGod opened this issue Sep 21, 2022 · 1 comment · Fixed by #3216
Labels
bug Something isn't working
Milestone

Comments

@MadVikingGod
Copy link
Contributor

Description

When attempting to pull the sdk/metric alpha you get an error:

go: downloading go.opentelemetry.io/otel/sdk v0.0.0-00010101000000-000000000000
go.opentelemetry.io/otel/sdk/metric imports
        go.opentelemetry.io/otel/sdk/instrumentation: go.opentelemetry.io/otel/[email protected]: invalid version: unknown revision 000000000000
go.opentelemetry.io/otel/sdk/metric imports
        go.opentelemetry.io/otel/sdk/resource: go.opentelemetry.io/otel/[email protected]: invalid version: unknown revision 000000000000

This is because the go.mod has an entry:

go.opentelemetry.io/otel/sdk v0.0.0-00010101000000-000000000000

Environment

  • OS: linux
  • Architecture: amd64
  • Go Version: 1.19
  • opentelemetry-go version: sdk/metrics v0.32.0

Steps To Reproduce

  1. Start a new project go mod init main
  2. Pull the metric SDK, go get go.opentelemetry.io/otel/sdk/metric

Expected behavior

We should be able to go get the SDK without a problem.

@williambrode
Copy link

I wonder if a step could be added to CI to just go get all the modules? Just a thought on how to prevent it in the future.

@pellared pellared added this to the untracked milestone Nov 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants