Recordsgolanggo.opentelemetry.io/otel/exporters/otlp/otlptrace/otlptracegrpcv1.35.0WithTimeout
shared with 2 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/exporters/otlp/otlptrace/otlptracegrpc v1.35.0: WithTimeout 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. HOWWithTimeout MIT-0 · 2026-09-02
- go.opentelemetry.io/otel/exporters/otlp/otlptrace/otlptracegrpc v1.35.0: WithTimeout 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. HOWotlptracegrpc.WithTimeout MIT-0 · 2026-09-02
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✓ 2✕
|
ELEVATED FAILURE | 1 | 3 | 35% | 1 · 1✓ | 2026-09-14 |
| go 1.26 · Go · go · linux glibc
Observations: PROJECT_COMPILE 0✓ 1✕ · PROJECT_PROCESS 5✓ · PROJECT_TEST 2✓
|
LOW | 8 | 0 | 88% | 1 | 2026-09-02 |
snapshot · 2026-09-15
Failure clusters
-
observed PROJECT_TEST Evidence gap ×4 v1.35.0 → v1.43.0 executionContext=go · os=linux · runtime=go@1.26Evidence quality: legacy-evidence-incomplete · Environment variants: 2 · First recorded: 2026-09-01 · Last seen: 2026-09-03Diagnostic re-verification candidate
-
observed PROJECT_COMPILE exit 1 ×1 v1.35.0 os=linux · runtime=go@1.26 sha256:e84876b56a4e…test/contract.go:<n>:<n>: assignment mismatch: 1 variable but otlptrace.New returns 2 values …go/compiler · compiler-diagnostic · outer go runEvidence quality: complete · Environment variants: 1 · First recorded: 2026-09-02 · Last seen: 2026-09-02
-
observed PROJECT_TEST exit 1 ×1 v1.35.0 os=linux · runtime=go@1.26 sha256:4d9975558e16…--- FAIL: TestWithoutInsecureFailsPlaintext (10.00s) · FAIL example.com/otlptracegrpc-insecure/test 10.009sgo/test · test-runner-diagnostic · outer go testEvidence quality: complete · Environment variants: 1 · First recorded: 2026-09-02 · Last seen: 2026-09-02
-
observed PROJECT_TEST exit 1 ×1 v1.35.0 os=linux · runtime=go@1.26 sha256:b6b84f5f81cf…--- FAIL: TestWithInsecureContract (10.00s) · contract_test.go:<n>: expected at least one gRPC trace export request, got none …go/test · test-runner-diagnostic · outer go testEvidence quality: complete · Environment variants: 1 · First recorded: 2026-09-02 · Last seen: 2026-09-02