Recordsgolanggithub.com/envoyproxy/go-control-planev0.9.1-0.20191026205805-5f8ba28d4473
Which symbol ran where
Symbols × operating systems for this version. Cells drill into the package's compatibility cube.
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 2✓ · PROJECT_TEST 2✓ — Usage: USED 5✓ — Verified: CONTRACT 2✓
|
LOW | 4 +5 | 2 | 100% | 1 · 1✓ | 2026-10-21 |
| go 1.26 · Go · go · linux glibc
Observations: PROJECT_COMPILE 0✓ 1✕ · PROJECT_PROCESS 3✓ — Usage: USED 2✓
|
LOW | 4 +2 | 0 | 75% | 1 | 2026-10-17 |
Recent failure clusters
-
observed PROJECT_COMPILE exit 1 ×1 v0.9.1-0.20191026205805-5f8ba28d4473 os=linux · runtime=go@1.26 github.com/envoyproxy/go-control-plane/envoy/api/v2.Cluster sha256:ef84e7f7e32b…test/contract.go:<n>:<n>: not enough arguments in call to cache.NewSnapshotgo/compiler · compiler-diagnostic · outer go runEvidence quality: complete · Environment variants: 1 · First recorded: 2026-10-17 · Last seen: 2026-10-17
Symbols
- github.com/envoyproxy/go-control-plane/envoy/api/v2/core.Address
- github.com/envoyproxy/go-control-plane/envoy/api/v2/core.Address_SocketAddress
- github.com/envoyproxy/go-control-plane/envoy/api/v2.Cluster 1 1 of 1 runs passed
- github.com/envoyproxy/go-control-plane/pkg/cache.ClusterType
- github.com/envoyproxy/go-control-plane/envoy/api/v2.Cluster_LOGICAL_DNS
- github.com/envoyproxy/go-control-plane/envoy/api/v2.Cluster_ROUND_ROBIN
- github.com/envoyproxy/go-control-plane/envoy/api/v2.Cluster_Type
- github.com/envoyproxy/go-control-plane/envoy/api/v2.Cluster_V4_ONLY
- github.com/envoyproxy/go-control-plane/pkg/cache.IDHash
- github.com/envoyproxy/go-control-plane/pkg/cache.NewSnapshot
- github.com/envoyproxy/go-control-plane/pkg/cache.NewSnapshotCache
- github.com/envoyproxy/go-control-plane/envoy/api/v2/core.Node
- github.com/envoyproxy/go-control-plane/pkg/cache.Resource
- github.com/envoyproxy/go-control-plane/pkg/cache.RouteType
- github.com/envoyproxy/go-control-plane/envoy/api/v2/core.SocketAddress
- github.com/envoyproxy/go-control-plane/envoy/api/v2/core.SocketAddress_PortValue
Published samples
- github.com/envoyproxy/go-control-plane v0.9.1-0.20191026205805-5f8ba28d4473 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-10-17