CodeSampleX

Recordsgolanggoogle.golang.org/protobuffailure issue

Failure signature

PROJECT_RESOLVE exit 1 ×1

main.go:<n>:<n>: missing go.sum entry for module providing package google.golang.org/genproto/googleapis/rpc/errdetails (imported by example.com/sample); to …

Evidence quality: complete · go/module · resolve-diagnostic · outer go build · First recorded: 2026-08-31 · Last seen: 2026-08-31

sha256:cd8897765ac3…

google.golang.org/protobuf/encoding/protojson.Marshal google.golang.org/protobuf/encoding/protojson.Unmarshal google.golang.org/protobuf/proto.Equal google.golang.org/protobuf/proto.Marshal google.golang.org/protobuf/proto.Unmarshal google.golang.org/protobuf/types/known/anypb.Any google.golang.org/protobuf/types/known/anypb.New

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.

Moved: 1 · 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

Published answers for the affected releases

Back to the package