Recordsgolanggithub.com/envoyproxy/go-control-planev0.14.0github.com/envoyproxy/go-control-plane/pkg/cache/v3.IDHash
OS × runtime at a glance
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.
Published samples
- github.com/envoyproxy/go-control-plane v0.14.0: v3.IDHash 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. HOWgithub.com/envoyproxy/go-control-plane/pkg/cache/v3.IDHash MIT-0 · 2026-09-15
Compatibility matrix
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_TEST 2✓ — Verified: CONTRACT 1✓
|
LOW | 2 | 1 | 100% | 1 · 1✓ | 2026-09-17 |
| go 1.26 · Go · go · linux glibc
Observations: PROJECT_PROCESS 3✓
|
LOW | 3 | 0 | 100% | 1 | 2026-09-15 |
snapshot · 2026-09-17
Failure clusters
-
observed UNKNOWN exit 1 Evidence gap ×3 v0.14.0 os=linux · runtime=go@1.26 sha256:3b3190f2cd44…doc: cannot find package <str> in any of: · ($GOROOT not set) · <path> (from $GOPATH)go · unclassified-diagnostic · outer go · gap stage-unknownEvidence quality: complete · Environment variants: 1 · First recorded: 2026-09-14 · Last seen: 2026-09-15Diagnostic re-verification candidate
-
observed PROJECT_RESOLVE exit 1 ×1 v0.14.0 os=linux · runtime=go@1.26 sha256:aa0961c9bc5e…<path>:<n>:<n>: missing go.sum entry for module providing package google.golang.org/protobuf/proto (imported by …go/module · resolve-diagnostic · outer go listEvidence quality: complete · Environment variants: 1 · First recorded: 2026-09-14 · Last seen: 2026-09-14
-
observed UNKNOWN exit 1 Evidence gap ×1 v0.14.0 os=linux · runtime=go@1.26 sha256:17ac37c84e76…doc: no such package: github.com/envoyproxy/go-control-<token>go · unclassified-diagnostic · outer go · gap stage-unknownEvidence quality: complete · Environment variants: 1 · First recorded: 2026-09-14 · Last seen: 2026-09-14Diagnostic re-verification candidate
-
observed PROJECT_RESOLVE exit 1 ×1 v0.14.0 os=linux · runtime=go@1.26 sha256:a49282d01fb2…main.go:<n>:<n>: missing go.sum entry for module providing package github.com/envoyproxy/go-control-<token> (imported by probe); to add: …go/module · resolve-diagnostic · outer go runEvidence quality: complete · Environment variants: 1 · First recorded: 2026-09-15 · Last seen: 2026-09-15