Recordsgolanggo.opentelemetry.io/otel/sdk/metricfailure issue
Failure signature
PROJECT_COMPILE exit 1 ×2
test/contract.go:<n>:<n>: <str> imported and not used
Evidence quality: complete · go/compiler · compiler-diagnostic · outer go run · First recorded: 2026-08-31 · Last seen: 2026-09-01
sha256:d5fae02e8604…
go.opentelemetry.io/otel/sdk/metric.Aggregation go.opentelemetry.io/otel/sdk/metric.AggregationDrop go.opentelemetry.io/otel/sdk/metric.AggregationExplicitBucketHistogram go.opentelemetry.io/otel/sdk/metric.AggregationSelector go.opentelemetry.io/otel/sdk/metric.DefaultAggregationSelector go.opentelemetry.io/otel/sdk/metric.InstrumentKind go.opentelemetry.io/otel/sdk/metric.InstrumentKindCounter go.opentelemetry.io/otel/sdk/metric.InstrumentKindHistogram go.opentelemetry.io/otel/sdk/metric.InstrumentKindObservableCounter go.opentelemetry.io/otel/sdk/metric.MeterProvider go.opentelemetry.io/otel/sdk/metric.NewMeterProvider go.opentelemetry.io/otel/sdk/metric.NewPeriodicReader go.opentelemetry.io/otel/sdk/metric.WithReader go.opentelemetry.io/otel/sdk/metric/metricdata.CumulativeTemporality go.opentelemetry.io/otel/sdk/metric/metricdata.DataPoint go.opentelemetry.io/otel/sdk/metric/metricdata.Metrics go.opentelemetry.io/otel/sdk/metric/metricdata.ResourceMetrics go.opentelemetry.io/otel/sdk/metric/metricdata.ScopeMetrics go.opentelemetry.io/otel/sdk/metric/metricdata.Sum
Where it was measured
PASS means the release recorded a passing observation at PROJECT_COMPILE and no record of this failure. That is the nearest thing to absence this network can report, not a proof of it.
- v1.46.0 PASS 5 passing observations
- v1.45.0 not measured
- v1.44.0 not measured
- v1.43.0 FAIL
- v1.40.0 not measured
- v1.37.0 not measured
- v1.34.0 not measured
Where it reproduced
- os=linux · runtime=go@1.26 ×2 2026-08-31 → 2026-09-01
Nearest known PASS/FAIL boundaries
The two adjacent releases the verdict changes across. Releases nothing measured do not close the gap; they are counted instead.
-
Last failing release v1.43.0 → first passing release v1.46.0
Releases between them never measured at this stage: 2
What differs across the boundary
- github.com/go-logr/logr v1.4.4 → v1.4.3 hypothesis
- github.com/stretchr/testify v1.12.1 → v1.11.1 hypothesis
- go.opentelemetry.io/otel v1.46.0 → v1.43.0 hypothesis
- go.opentelemetry.io/otel/metric v1.46.0 → v1.43.0 hypothesis
- go.opentelemetry.io/otel/metric/x v0.68.0 → — hypothesis
- go.opentelemetry.io/otel/sdk v1.46.0 → v1.43.0 hypothesis
- go.opentelemetry.io/otel/trace v1.46.0 → v1.43.0 hypothesis
A version that moved across the boundary is a candidate, not a cause. Only a receipt that recorded the failure and the tree it resolved in the same run is marked as evidence.
Dependency versions across releases
What each release of this package resolved its children to. A child whose version moved is listed first: that is where an upgrade changed something underneath you.
Moved: 8 · unchanged at every release: 1
An edge records that a resolver placed one release beside another on a real machine. It is not a claim that the two work together; that question is answered by samples and contracts, not by presence here.
Evidence gaps
- Releases in this window never measured at PROJECT_COMPILE: 5
- No failure domain was inferred for this failure.
Published answers for the affected releases
- go.opentelemetry.io/otel/sdk/metric v1.43.0: create meter provider with manual reader and collect metrics This network offers one thing: a sample that builds. It ran the sample in a sandbox and kept the signed receipt. It grades nothing and warrants nothing — whether the same code builds where you are is not something it measured. HOWNewManualReaderNewMeterProvidergo MIT-0 · 2026-08-28