Recordsgolanggoogle.golang.org/genprotofailure issue
Failure signature
PROJECT_COMPILE exit 1 ×1
<path>:<n>:<n>: undefined: descriptorpb.Default_FileOptions_PhpGenericServices
Evidence quality: complete · go/compiler · compiler-diagnostic · outer go run · First recorded: 2026-10-13 · Last seen: 2026-10-13
sha256:6124cc672b33…
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.0.0-20200825200019-8632dd797987 PASS 1 passing observations
- v0.0.0-20200804131852-c06518451d9c not measured
- v0.0.0-20200618031413-b414f8b61790 not measured
- v0.0.0-20200331122359-1ee6d9798940 not measured
- v0.0.0-20190819201941-24fa4b261c55 FAIL
- v0.0.0-20190306203927-b5d61aea6440 not measured
- v0.0.0-20181202183823-bd91e49a0898 not measured
- v0.0.0-20180817151627-c66870c02cf8 PASS 1 passing observations
Where it reproduced
- os=linux · runtime=go@1.26 ×1 2026-10-13 → 2026-10-13
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 passing release v0.0.0-20180817151627-c66870c02cf8 → first failing release v0.0.0-20190819201941-24fa4b261c55
Releases between them never measured at this stage: 2
One side of this boundary has no resolved dependency tree, so nothing could be compared.
-
Last failing release v0.0.0-20190819201941-24fa4b261c55 → first passing release v0.0.0-20200825200019-8632dd797987
Releases between them never measured at this stage: 3
What differs across the boundary
- github.com/golang/protobuf v1.4.2, v1.5.0, v1.5.2 → v1.3.2, v1.3.3, v1.5.4 hypothesis
- golang.org/x/exp — → v0.0.0-20190121172915-509febef88a4 hypothesis
- golang.org/x/lint v0.0.0-20200302205851-738671d3881b → v0.0.0-20190313153728-d0100b6bd8b3 hypothesis
- golang.org/x/tools v0.0.0-20200825202427-b303f430e36d, v0.1.12 → v0.0.0-20190524140312-2c0ae7006135, v0.44.0 hypothesis
- google.golang.org/grpc v1.31.0 → v1.25.1, v1.31.0, v1.34.0-dev hypothesis
- google.golang.org/protobuf v1.26.0, v1.36.11, v1.36.12 → — hypothesis
- honnef.co/go/tools — → v0.0.0-20190523083050-ea95bdfd59fc 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: 7 · unchanged at every release: 1
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: 5
- No resolved dependency tree for v0.0.0-20180817151627-c66870c02cf8 or for v0.0.0-20190819201941-24fa4b261c55, so the versions either side of the boundary could not be compared.
- No failure domain was inferred for this failure.
Published answers for the affected releases
No published sample names these releases.