CodeSampleX

Recordsgolanggoogle.golang.org/genproto/googleapis/rpcfailure issue

Failure signature

PROJECT_RESOLVE exit 1 ×2

<path> missing go.sum entry for module providing package google.golang.org/protobuf/reflect/protoreflect (imported by …

Evidence quality: complete · go/module · resolve-diagnostic · outer go test · First recorded: 2026-08-30 · Last seen: 2026-09-04

sha256:8d36c74400d3…

Where it was measured

PASS means the release recorded a passing observation at PROJECT_RESOLVE and no record of this failure. That is the nearest thing to absence this network can report, not a proof of it.

Where it reproduced

Nearest known PASS/FAIL boundaries

No release either side of this failure recorded a passing observation at this stage, so where it starts and stops is not established.

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.

Libraryv0.0.0-20260904194346-d0f1323225a4v0.0.0-20260831171406-18b4a7587f8av0.0.0-20260825221802-da73d73af1c5v0.0.0-20260819154853-08b0e4226688v0.0.0-20250218202821-56aae31c358av0.0.0-20250115164207-1a7da9e5054fv0.0.0-20241007155032-5fefd90f89a9v0.0.0-20240826202546-f6391c0de4c7v0.0.0-20240814211410-ddb44dafa142
google.golang.org/protobuf v1.36.12 v1.36.12 v1.36.12 v1.36.12 v1.36.5 v1.36.5 v1.35.1 v1.34.2 v1.34.2

Moved: 1 · unchanged at every release: 0

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

Published answers for the affected releases

Back to the package