Recordsgolanggo.uber.org/zapv1.27.0
Which symbol ran where
Symbols × operating systems for this version. Cells drill into the package's compatibility cube.
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.
Environment detail
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 5✓ 1✕ — Verified: UNKNOWN 0✓ 3✕
|
ELEVATED FAILURE | 6 | 3 | 56% | 1 | 2026-08-29 |
| go 1.26 · Go · go · linux musl · docker
Observations: PROJECT_LOAD 4✓ · PROJECT_TEST 4✓ — Usage: USED 4✓ — Verified: CONTRACT 4✓
|
MEDIUM | 8 +4 | 4 | 100% | 1 · 2✓ | 2026-08-30 |
| go 1.26 · Go · go · windows
Observations: PROJECT_TEST 7✓
|
LOW | 7 | 0 | 100% | 1 | 2026-08-17 |
Recent failure clusters
-
observed PROJECT_PROCESS Evidence gap ×1 v1.27.0 os=linux · runtime=go@1.26Evidence quality: legacy-evidence-incomplete · Environment variants: 1 · First recorded: 2026-08-26 · Last seen: 2026-08-26
-
observed UNKNOWN exit 1 Evidence gap ×1 v1.27.0 os=linux · runtime=go@1.26 sha256:23ccd0c7b557…FAIL: expected 168h for 1w, got 0s (err: time: unknown unit <str> in duration <str>) · exit status 1go · unclassified-diagnostic · outer go run · gap stage-unknownEvidence quality: complete · Environment variants: 1 · First recorded: 2026-08-29 · Last seen: 2026-08-29Diagnostic re-verification candidate
-
observed UNKNOWN exit 1 Evidence gap ×1 v1.27.0 os=linux · runtime=go@1.26 sha256:2470d64a481a…# example.com/sample/test · test/contract.go:<n>:<n>: dur.UnmarshalText undefined (type caddy.Duration has no field or method UnmarshalText)go · unclassified-diagnostic · outer go run · gap stage-unknownEvidence quality: complete · Environment variants: 1 · First recorded: 2026-08-29 · Last seen: 2026-08-29Diagnostic re-verification candidate
-
observed UNKNOWN exit 1 Evidence gap ×1 v1.27.0 os=linux · runtime=go@1.26 sha256:31bc65941ca5…# example.com/sample/test · test/contract.go:<n>:<n>: dur.String undefined (type caddy.Duration has no field or method String) …go · unclassified-diagnostic · outer go run · gap stage-unknownEvidence quality: complete · Environment variants: 1 · First recorded: 2026-08-29 · Last seen: 2026-08-29Diagnostic re-verification candidate
Symbols
- zap.Config.Build 2 of 2 runs passed
- zap.RegisterSink 2 of 2 runs passed
Published samples
- go.uber.org/zap v1.27.0 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. HOW MIT-0 · 2026-08-19
- go.uber.org/zap v1.27.0 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. HOW MIT-0 · 2026-08-19