CodeSampleX

Recordsgolanggo.opentelemetry.io/otelv1.43.0go.opentelemetry.io/otel/codes.Ok

Change the conditions
Fixed
Package versionv1.43.0 Symbolgo.opentelemetry.io/otel/codes.Ok
Filter OSubuntu glibc Runtimego 1.26 Architecturex64 Package managergo 1 libcglibc Clear filters

Current conditions

go.opentelemetry.io/otel/codes.Ok @v1.43.0ubuntu glibc · x64 · go 1.26 · go 1

0 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 failed

Project observations
3 / 3
Contract verifications
0 / 1
Independent reporting peers
1
Last recorded
2026-08-31

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Changed 7 · Steady 2

First observed break

v1.43.0

linux

16 FAIL · stage: PROCESS_START · fingerprint: sha256:c12549970456efb5abdc90b679695c6689107d4f097d612245d6bfb25e01ec32

Library Version Health Measured there Projects
github.com/go-logr/logr v1.4.3 CANDIDATE Correlated change; unproven combination contract passed 64 project-days
github.com/go-logr/logr v1.4.4 CANDIDATE Correlated change; unproven combination contract passed 1 project-day
github.com/google/go-cmp v0.7.0 CANDIDATE Correlated change; unproven combination contract passed 63 project-days
github.com/stretchr/testify v1.11.1 CANDIDATE Correlated change; unproven combination contract passed 62 project-days
go.opentelemetry.io/auto/sdk v1.2.1 CANDIDATE Correlated change; unproven combination contract passed 64 project-days
go.opentelemetry.io/otel/metric v1.43.0 CANDIDATE Correlated change; unproven combination contract passed 65 project-days
go.opentelemetry.io/otel/trace v1.43.0 CANDIDATE Correlated change; unproven combination contract passed 65 project-days
github.com/cespare/xxhash/v2 v2.3.0 PASS All observations passed contract passed 64 project-days
github.com/go-logr/stdr v1.2.2 PASS All observations passed contract passed 65 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: 6 · unchanged at every release: 3

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

Showing the 12 most-reported of 84 recorded failure clusters. The rest are single reports.