CodeSampleX

Recordsgolanggo.opentelemetry.io/otelv1.47.0otel.GetErrorHandler

Change the conditions
Fixed
Package versionv1.47.0 Symbolotel.GetErrorHandler
Filter OSdebian glibc Runtimego 1.26 Architecturex64 Package managergo Execution contextgo libcglibc Clear filters

Current conditions

otel.GetErrorHandler @v1.47.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 (1)

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

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Changed 6 · Steady 3

First observed break

v1.47.0

linux · go@1.26

1 FAIL · stage: PROJECT_COMPILE · fingerprint: sha256:947b5eb5acb22df3e2b467a63ac602c8f2404752e554dadc9e0ac8d207dfca37

Library Version Health Measured there Projects
github.com/go-logr/logr v1.4.4 CANDIDATE Correlated change; unproven combination contract passed 8 project-days
github.com/google/go-cmp v0.7.0 CANDIDATE Correlated change; unproven combination contract passed 8 project-days
github.com/stretchr/testify v1.12.1 CANDIDATE Correlated change; unproven combination builds observed 8 project-days
go.opentelemetry.io/auto/sdk v1.2.1 CANDIDATE Correlated change; unproven combination contract passed 8 project-days
go.opentelemetry.io/otel/metric v1.47.0 CANDIDATE Correlated change; unproven combination contract passed 8 project-days
go.opentelemetry.io/otel/trace v1.47.0 CANDIDATE Correlated change; unproven combination contract passed 8 project-days
github.com/cespare/xxhash/v2 v2.3.0 PASS All observations passed contract passed 8 project-days
github.com/go-logr/stdr v1.2.2 PASS All observations passed contract passed 8 project-days
go.opentelemetry.io/otel/log v1.47.0 PASS All observations passed contract passed 8 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