-
Notifications
You must be signed in to change notification settings - Fork 1k
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
go get all: module go.opentelemetry.io/otel/metric@upgrade found (v0.30.0), but does not contain package #2938
Comments
It seems |
This will happen if you are upgrading past metric v0.27.0. Those packages were removed with the new API. Please understand that the metrics API and SDK are in flux and are not considered stable, so there can be breaking changes in the future. |
@dmathieu https://github.com/open-telemetry/opentelemetry-go/blob/main/bridge/opencensus/go.mod#L10 The releases also seem to indicate that v0.30.0 was just released alongside v1.7.0. Maybe metrics go modules are being released at different versions? EDIT -- sorry, I apparently had a frozen version of the bridge. Things are working for me. Left for reference -- got around the issue by explicitly upgrading the bridge package
I understand that the metrics apis are not considered stable but this issue seems to be internal to the OTEL go libraries. |
I get something similar
|
UPDATE:
$ go get -u
$ go mod tidy
go: finding module for package go.opentelemetry.io/otel/metric/number
...cmd/devices imports
go.opentelemetry.io/otel/exporters/metric/prometheus imports
go.opentelemetry.io/otel/metric/number: module go.opentelemetry.io/otel/metric@latest found (v0.30.0), but does not contain package go.opentelemetry.io/otel/metric/number I am also facing this problem. I have tried to force the latest package versions in different combinations, but without success. $ go mod tidy
go: finding module for package go.opentelemetry.io/otel/semconv
go: finding module for package go.opentelemetry.io/otel/unit
go: finding module for package go.opentelemetry.io/otel/internal/metric
go: found go.opentelemetry.io/otel/internal/metric in go.opentelemetry.io/otel/internal/metric v0.27.0
go: finding module for package go.opentelemetry.io/otel/semconv
go: finding module for package go.opentelemetry.io/otel/unit
go: finding module for package go.opentelemetry.io/otel/metric/registry
.../cmd/devices imports
go.opentelemetry.io/contrib/instrumentation/runtime imports
go.opentelemetry.io/otel/unit: module go.opentelemetry.io/otel@latest found (v1.7.0), but does not contain package go.opentelemetry.io/otel/unit
.../cmd/devices imports
go.opentelemetry.io/otel/sdk/metric/controller/basic imports
go.opentelemetry.io/otel/metric/registry: module go.opentelemetry.io/otel/metric@latest found (v0.30.0), but does not contain package go.opentelemetry.io/otel/metric/registry
.../cmd/devices imports
go.opentelemetry.io/contrib/instrumentation/runtime tested by
go.opentelemetry.io/contrib/instrumentation/runtime.test imports
go.opentelemetry.io/otel/oteltest imports
go.opentelemetry.io/otel/semconv: module go.opentelemetry.io/otel@latest found (v1.7.0), but does not contain package go.opentelemetry.io/otel/semconv
|
THe issue on my side is related to this deprecation: https://github.com/open-telemetry/opentelemetry-go/blob/main/CHANGELOG.md#deprecated-6 replace
By
FIxed for me |
I'm facing a similar issue. Is there an update? |
Similar issue here as well. Trying to use otlphttp.
Current contents in go.mod:
|
Sorry, my case was due to me importing it wrong. I should have been using go.opentelemetry.io/otel/exporters/otlp/otlptrace/otlptracehttp |
I'm facing a similar issue. Is there an update? |
This issue will happen if one of your otel packages is still using v0.x, and not 1.x. The fix is to upgrade every OpenTelemetry pakage to 1.x. |
This is in general good, but not entirely complete advice as some otel packages like In my case, when I updated to the
If you go to https://pkg.go.dev/go.opentelemetry.io/otel/metric/nonrecording you can see in the latest release that the Upgrading
Running After we are able to upgrade to Go 1.17 and then update otelsql, we can remove the replace directive and allow go.opentelemetry.io/otel/metric to advance to v0.31.0. I hope this is helpful to others who have similar problems. |
If you upgrade otelsql to 0.16.0, this metric issue should be fixed. |
Closing as the original author has resolved their issue. |
Still have this error with |
Please open a new issue to address your situation. |
go get -u all
go get all: module go.opentelemetry.io/otel/metric@upgrade found (v0.30.0), but does not contain package go.opentelemetry.io/otel/metric/number
go get all: module go.opentelemetry.io/otel/metric@upgrade found (v0.30.0), but does not contain package go.opentelemetry.io/otel/metric/sdkapi
The text was updated successfully, but these errors were encountered: