Recordsgolanggo.opentelemetry.io/otel/tracev1.37.0go.opentelemetry.io/otel/trace.ContextWithSpan
shared with 3 packages — this evidence cannot say whose API it is
OS × runtime at a glance
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.
- no sample at this coordinate yet
- there is a sample here, and nothing of ours has run it at this coordinate yet
- there is a sample here, and our run of it at this coordinate came back clean
- there is a sample here, and our run of it at this coordinate failed
- there is a sample here, and this coordinate records both a passing and a failing run of it
- nothing recorded — unknown, never "works" and never "broken"
- there is a level below this cell — click to open it
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
- go.opentelemetry.io/otel/trace v1.37.0: ContextWithSpan 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.ContextWithSpan MIT-0 · 2026-09-17
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 · docker
Observations: PROJECT_TEST 1✓ — Verified: CONTRACT 1✓
|
LOW | 1 | 1 | 100% | 1 · 1✓ | 2026-09-17 |
| go 1.26 · Go · go · linux glibc
Observations: PROJECT_COMPILE 0✓ 1✕ · PROJECT_PROCESS 2✓ — Verified: UNKNOWN 0✓ 1✕
|
LOW | 3 | 1 | 50% | 1 | 2026-09-17 |
snapshot · 2026-09-17
Failure clusters
-
observed PROJECT_COMPILE exit 1 ×1 os=linux · runtime=go@1.26 sha256:dea3f615d3b9…test/contract.go:<n>:<n>: invalid operation: retrieved.SpanContext() != sc (struct containing trace.TraceState cannot be compared) …go/compiler · compiler-diagnostic · outer go runEvidence quality: complete
-
observed UNKNOWN exit 1 Evidence gap ×1 os=linux · runtime=go@1.26 sha256:e5f033e5b6e3…Contract test failed: child span from noop tracer should have invalid span context · exit status 1go · unclassified-diagnostic · outer go run · gap stage-unknownEvidence quality: complete