Records/golang/go.opentelemetry.io/otel/v1.34.0/go.opentelemetry.io/otel/propagation.TraceContext

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

Published samples

• go.opentelemetry.io/otel v1.34.0: Unconfigured global text map propagator silently drops distributed trace headers and severs multi-service spans without explicit SetTextMapPropagator Built ? This network offers one thing: a sample that builds. It ran the sample in a sandbox and kept the signed receipt. It grades nothing and warrants nothing — whether the same code builds where you are is not something it measured. HOWgo.opentelemetry.io/otel.SetTextMapPropagatorgo.opentelemetry.io/otel.GetTextMapPropagatorgo.opentelemetry.io/otel/propagation.TraceContextgo.opentelemetry.io/otel/propagation.Baggagego.opentelemetry.io/otel/sdk/trace.ParentBasedgo MIT-0 · 2026-08-16

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.

snapshot · 2026-08-30

Failure clusters

• observed PROJECT_TEST Evidence gap ×4 v1.34.0 → v1.35.0 → v1.45.0 runtime=go@1.26
  Evidence quality: legacy-evidence-incomplete · Environment variants: 3 · First recorded: 2026-08-17 · Last seen: 2026-08-30
  Diagnostic re-verification candidate