CodeSampleX

Recordsgolanggo.opentelemetry.io/otel/tracev1.45.0go.opentelemetry.io/otel/trace.SpanFromContext

shared with 2 packages — this evidence cannot say whose API it is

OS × runtime at a glance

1○ 12026-09-10
go 1.26
alpine musl —
ubuntu glibc 60%5

Reading a cell: The number is how many recorded observations the rate divides — one build files an observation per stage it reached, so it counts neither builds nor machines nor people. The document beside it is a different fact from a different source: whether a sample exists at that coordinate, and how our own run of it went there.

A document means there is a sample at that coordinate. Whether one EXISTS is a fact about this release and this API and does not change with OS, runtime or package manager; its COLOUR is how that sample ran in the environment you are looking at.

Published samples

Compatibility matrix

Project-level observations and symbol/contract verifications are counted separately and never combined.

These counts do not distinguish how the symbol was called: overloads, argument shapes and options are pooled together. What a particular call shape does is proven by a sample's contract, not by these numbers.

Environment Confidence Observations Verified Pass rate Peers Last seen
go 1.26 · Go · go · linux glibc
Observations: PROJECT_PROCESS 2✓ · PROJECT_RESOLVE 0✓ 1✕ · PROJECT_TEST 1✓ 1✕
ELEVATED FAILURE 5 0 60% 1 2026-09-10
go 1.26 · Go · gomod · linux musl · docker
Verified: CONTRACT 3✓ 3✕
ELEVATED FAILURE 0 6 50% 0 · 2✓ 2026-09-07

snapshot · 2026-09-15

Failure clusters