envoyv1.36.0

Which symbol ran where

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

6○ 62026-09-17

	debian glibc	ubuntu glibc
github.com/envoyproxy/go-control-plane/envoy/config/cluster/v3.Cluster	100%2	100%26
github.com/envoyproxy/go-control-plane/envoy/config/cluster/v3.Cluster_DiscoveryType	100%2	100%16
github.com/envoyproxy/go-control-plane/envoy/config/cluster/v3.Cluster_DiscoveryType_name	100%2	100%13
github.com/envoyproxy/go-control-plane/envoy/config/cluster/v3.Cluster_DiscoveryType_value	100%2	100%11
github.com/envoyproxy/go-control-plane/envoy/config/cluster/v3.Cluster_EDS	100%2	100%10
github.com/envoyproxy/go-control-plane/envoy/config/cluster/v3.Cluster_LOGICAL_DNS	100%2	100%15

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 5✓ · PROJECT_TEST 5✓ — Usage: USED 5✓ — Verified: CONTRACT 17✓	LOW	10 +5	17	100%	1 · 1✓	2026-09-17
go 1.26 · Go · go · linux glibc Observations: PROJECT_PROCESS 40✓ — Usage: USED 24✓ — Verified: UNKNOWN 0✓ 1✕	LOW	40 +24	1	98%	1	2026-09-15

Recent failure clusters

observed UNKNOWN exit 1 Evidence gap ×1 v1.36.0 os=linux · runtime=go@1.26 github.com/envoyproxy/go-control-plane/envoy/config/core/v3.Address sha256:f9232a56ee73…
# sample/test · test/contract.go:<n>:<n>: name isAddress_Address not exported by package corev3
go · unclassified-diagnostic · outer go run · gap stage-unknown

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

Diagnostic re-verification candidate

Where does this failure start and stop?

Symbols

Published samples

github.com/envoyproxy/go-control-plane/envoy v1.36.0 HOWgo 1.26.7 MIT-0 · 2026-09-14