Records golang google.golang.org/protobufv1.35.2

Which symbol ran where

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

62026-10-15

	debian glibc	ubuntu glibc
google.golang.org/protobuf/encoding/protojson.Marshal		100%1
google.golang.org/protobuf/encoding/protojson.MarshalOptions		100%1
google.golang.org/protobuf/encoding/protojson.Unmarshal		100%1
google.golang.org/protobuf/proto.Bool		100%3
google.golang.org/protobuf/proto.Int32		100%3
google.golang.org/protobuf/proto.Marshal		100%3

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 2✓ — Verified: CONTRACT 1✓	LOW	2 +2	1	100%	1 · 1✓	2026-10-15
go 1.26 · Go · go · linux glibc Observations: PROJECT_COMPILE 1✓ · PROJECT_PROCESS 6✓ · PROJECT_TEST 1✓ — Usage: USED 4✓ — Verified: UNKNOWN 0✓ 1✕	LOW	8 +4	1	89%	1	2026-10-15

Recent failure clusters

observed UNKNOWN exit 1 Evidence gap ×4 v1.33.0 → v1.35.2 → v1.36.11 os=linux · runtime=go@1.26 google.golang.org/protobuf/types/known/durationpb.New sha256:0882784d80c2…
go: build output <str> already exists and is a directory
go · unclassified-diagnostic · outer go build · gap stage-unknown

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

Diagnostic re-verification candidate

Where does this failure start and stop?

Symbols

Published samples

google.golang.org/protobuf v1.35.2 HOWgo MIT-0 · 2026-10-15