Recordsgolanggithub.com/envoyproxy/go-control-planefailure issue
Failure signature
PROJECT_COMPILE exit 1 ×1
test/contract.go:<n>:<n>: too many arguments in call to cache.NewSnapshot
Evidence quality: complete · go/compiler · compiler-diagnostic · outer go run · First recorded: 2026-10-16 · Last seen: 2026-10-16
sha256:93c0544f9507…
github.com/envoyproxy/go-control-plane/envoy/api/v2.Cluster github.com/envoyproxy/go-control-plane/envoy/api/v2/core.Node github.com/envoyproxy/go-control-plane/pkg/cache.ClusterType 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/pkg/cache.Resource github.com/envoyproxy/go-control-plane/pkg/cache.RouteType
Where it was measured
PASS means the release recorded a passing observation at PROJECT_COMPILE and no record of this failure. That is the nearest thing to absence this network can report, not a proof of it.
- v0.14.0 not measured
- v0.9.4 PASS 1 passing observations
- v0.9.1-0.20191026205805-5f8ba28d4473 not measured
- v0.9.0 FAIL
Where it reproduced
- os=linux · runtime=go@1.26 ×1 2026-10-16 → 2026-10-16
Nearest known PASS/FAIL boundaries
The two adjacent releases the verdict changes across. Releases nothing measured do not close the gap; they are counted instead.
-
Last failing release v0.9.0 → first passing release v0.9.4
Releases between them never measured at this stage: 1
What differs across the boundary
- github.com/cncf/udpa/go v0.0.0-20191209042840-269d4d468f6f → — hypothesis
- github.com/envoyproxy/protoc-gen-validate v0.1.0, v1.3.3 → v0.1.0 hypothesis
- github.com/golang/protobuf v1.3.2, v1.3.3, v1.3.5, v1.4.2, v1.5.0, v1.5.2, v1.5.4 → v1.3.2 hypothesis
- github.com/google/go-cmp v0.2.0, v0.4.0, v0.4.1, v0.5.1, v0.7.0 → — hypothesis
- github.com/prometheus/client_model v0.0.0-20190812154241-14fe0d1b01d4, v0.6.2, v0.6.3 → v0.0.0-20190812154241-14fe0d1b01d4 hypothesis
- google.golang.org/genproto v0.0.0-20190819201941-24fa4b261c55, v0.0.0-20200331122359-1ee6d9798940, v0.0.0-20200618031413-b414f8b61790, v0.0.0-20200804131852-c06518451d9c, v0.0.0-20200825200019-8632dd797987 → v0.0.0-20190819201941-24fa4b261c55 hypothesis
- google.golang.org/grpc v1.25.1, v1.28.0, v1.29.1, v1.31.0, v1.34.0-dev → v1.23.0, v1.25.1 hypothesis
A version that moved across the boundary is a candidate, not a cause. Only a receipt that recorded the failure and the tree it resolved in the same run is marked as evidence.
Dependency versions across releases
What each release of this package resolved its children to. A child whose version moved is listed first: that is where an upgrade changed something underneath you.
Moved: 6 · unchanged at every release: 8
An edge records that a resolver placed one release beside another on a real machine. It is not a claim that the two work together; that question is answered by samples and contracts, not by presence here.
Evidence gaps
- Releases in this window never measured at PROJECT_COMPILE: 2
- No failure domain was inferred for this failure.
Published answers for the affected releases
- github.com/envoyproxy/go-control-plane v0.9.0 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-16