CodeSampleX

Recordsgolanggo.opentelemetry.io/otel/exporters/stdout/stdouttracev1.43.0stdouttrace.Exporter.ExportSpans

Change the conditions
Fixed
OSdebian glibc Symbolstdouttrace.Exporter.ExportSpans
Filter Runtimego 1.26 Package versionv1.43.0 Architecturex64 Package managergo Execution contextgo libcglibc Clear filters

Current conditions

stdouttrace.Exporter.ExportSpans @v1.43.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
2 / 2
Contract verifications
1 / 1
Independent reporting peers
1
Last recorded
2026-09-17

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Changed 6 · Steady 0

First observed break

v1.43.0

linux · go@1.26

8 FAIL · stage: UNKNOWN · fingerprint: sha256:5782351ae918be51270d9cef1bb673332e715560dfddd80edfbf5b54ef128219

Library Version Health Measured there Projects
github.com/stretchr/testify v1.11.1 CANDIDATE Correlated change; unproven combination contract passed 9 project-days
go.opentelemetry.io/otel v1.43.0 CANDIDATE Correlated change; unproven combination contract passed 9 project-days
go.opentelemetry.io/otel/metric v1.43.0 CANDIDATE Correlated change; unproven combination contract passed 9 project-days
go.opentelemetry.io/otel/sdk v1.43.0 CANDIDATE Correlated change; unproven combination contract passed 9 project-days
go.opentelemetry.io/otel/sdk/metric v1.43.0 CANDIDATE Correlated change; unproven combination contract passed 9 project-days
go.opentelemetry.io/otel/trace v1.43.0 CANDIDATE Correlated change; unproven combination contract passed 9 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: 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

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