CodeSampleX

Recordsgolanggo.opentelemetry.io/otel/trace

Change the conditions
Fixed
Package versionv1.45.0 Symbolgo.opentelemetry.io/otel/trace.SpanFromContext
Filter Runtimego 1.26 Architecturex64 Execution contextgo Clear filters

Current conditions

go.opentelemetry.io/otel/trace.SpanFromContext @v1.45.0x64 · go 1.26 · go

3 of 6 passed

Verified — this network ran a contract at this coordinate.

there is a sample here, and this coordinate records both a passing and a failing run of it (3)

Project observations
3 / 5
Contract verifications
3 / 6
Independent reporting peers
1
Cross-checked
reproduced by two or more independent peers
Last recorded
2026-09-07

Exact records

This slice is down to its measured combinations — the environments below are exactly what ran.

Dependency Health

Observed combinations and failure evidence for this release

Observed problems 1 · Changed 3 · Steady 0

First observed break

v1.45.0

linux · go@1.26

3 FAIL · stage: PROJECT_TEST

Library Version Health Measured there Projects
github.com/google/go-cmp v0.7.0 CANDIDATE Correlated change; unproven combination contract passed 23 project-days
github.com/stretchr/testify v1.11.1 CANDIDATE Correlated change; unproven combination contract passed 23 project-days
go.opentelemetry.io/otel v1.45.0 CANDIDATE Correlated change; unproven combination contract passed 24 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: 3 · 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.