Records/golang/go.opentelemetry.io/otel/trace/v1.45.0/go.opentelemetry.io/otel/trace.ContextWithSpan

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

Published samples

• go.opentelemetry.io/otel/trace v1.45.0: SpanFromContext never returns nil on untraced contexts but yields invalid non-recording spans whose IDs format to 32-character and 16-character zero strings rather than empty strings, RecordError does not set error status, and NewSpanContext drops all fields if either TraceID or SpanID is zero 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/trace.SpanFromContextgo.opentelemetry.io/otel/trace.ContextWithSpango.opentelemetry.io/otel/trace.ContextWithRemoteSpanContextgo.opentelemetry.io/otel/trace.WithNewRootgo.opentelemetry.io/otel/trace.NewSpanContextgo.opentelemetry.io/otel/trace.TraceIDFromHexgo.opentelemetry.io/otel/trace.SpanIDFromHexgo.opentelemetry.io/otel/trace.Span.RecordErrorgo 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 ×2 v1.35.0 → v1.45.0 os=linux · runtime=go@1.26
  Evidence quality: legacy-evidence-incomplete · Environment variants: 2 · First recorded: 2026-08-20 · Last seen: 2026-08-30
  Diagnostic re-verification candidate