CodeSampleX

Recordsgolanggo.opentelemetry.io/otel/metricv1.24.0go.opentelemetry.io/otel/metric.Float64Histogram

Change the conditions
Fixed
OSdebian glibc Package versionv1.24.0 Symbolgo.opentelemetry.io/otel/metric.Float64Histogram
Filter Runtimego 1.26 Architecturex64 Package managergo Execution contextgo libcglibc Clear filters

Current conditions

go.opentelemetry.io/otel/metric.Float64Histogram @v1.24.0debian glibc · x64 · go 1.26 · go · go

1 of 1 passed

Verified — this network ran a contract at this coordinate.

there is a sample here, and our run of it at this coordinate came back clean (2)

Project observations
1 / 1
Contract verifications
1 / 1
Independent reporting peers
1
Last recorded
2026-09-16

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Changed 2 · Steady 0

First observed break

v1.24.0

linux · go@1.26

8 FAIL · stage: PROJECT_COMPILE · fingerprint: sha256:c2ae6d87252c4f443f14d40584c4012a25213fbf0bb7b5e35604e6d35d608229

Library Version Health Measured there Projects
github.com/stretchr/testify v1.8.4 CANDIDATE Correlated change; unproven combination contract passed 17 project-days
go.opentelemetry.io/otel v1.24.0 CANDIDATE Correlated change; unproven combination contract passed 17 project-days

The measured column is about each dependency's own release, not about the pair. A resolver placing two releases side by side is not evidence that they work together.

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: 2 · unchanged at every release: 0

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.

Recent failure clusters