rpcv0.0.0-20251029180050-ab9386a59fda

Which symbol ran where

Symbols × operating systems for this version. Cells drill into the package's compatibility cube.

4○ 62026-10-11

	debian glibc	ubuntu glibc
google.golang.org/genproto/googleapis/rpc/code.Code	100%1	100%13
google.golang.org/genproto/googleapis/rpc/code.Code_ABORTED		100%1
google.golang.org/genproto/googleapis/rpc/code.Code_ALREADY_EXISTS		100%1
google.golang.org/genproto/googleapis/rpc/code.Code_INTERNAL	100%1	100%7
google.golang.org/genproto/googleapis/rpc/code.Code_INVALID_ARGUMENT	100%1	100%7
google.golang.org/genproto/googleapis/rpc/code.Code_NOT_FOUND	100%1	100%7

Showing the environments with the most evidence.

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 · docker Observations: PROJECT_LOAD 1✓ · PROJECT_TEST 1✓ — Usage: USED 4✓ — Verified: CONTRACT 16✓	LOW	2 +4	16	100%	1 · 1✓	2026-10-11
go 1.26 · Go · go · linux glibc Observations: PROJECT_COMPILE 3✓ · PROJECT_PROCESS 56✓ · PROJECT_TEST 5✓ 1✕ — Usage: USED 23✓	LOW	65 +23	0	98%	1	2026-10-12
go 1.26 · Go · go · linux glibc · docker Usage: USED 1✓	LOW	0 +1	0	—	1	2026-10-12

Recent failure clusters

observed PROJECT_TEST exit 1 ×1 v0.0.0-20251029180050-ab9386a59fda os=linux · runtime=go@1.26 sha256:9495709474d2…
--- FAIL: TestCodesJSONSerialization (0.00s) · FAIL example.com/grpccodes/test 0.004s
go/test · test-runner-diagnostic · outer go test

Evidence quality: complete · Environment variants: 1 · First recorded: 2026-10-12 · Last seen: 2026-10-12

Where does this failure start and stop?

Symbols

Published samples

google.golang.org/genproto/googleapis/rpc v0.0.0-20251029180050-ab9386a59fda HOW MIT-0 · 2026-10-11