CodeSampleX

Recordsgolanggoogle.golang.org/protobuffailure issue

Failure signature

PROJECT_COMPILE exit 1 ×6

<path> <str> imported and not used

Evidence quality: complete · go/compiler · compiler-diagnostic · outer go run, go test · First recorded: 2026-08-30 · Last seen: 2026-09-07

sha256:964ddac6b19a…

google.golang.org/protobuf/encoding/protojson.Marshal google.golang.org/protobuf/encoding/protojson.MarshalOptions google.golang.org/protobuf/encoding/protojson.UnmarshalOptions google.golang.org/protobuf/types/known/fieldmaskpb.New google.golang.org/protobuf/types/known/structpb.Struct google.golang.org/protobuf/types/known/timestamppb.Now google.golang.org/protobuf/types/known/timestamppb.Timestamp google.golang.org/protobuf/types/known/wrapperspb.String

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.

Where it reproduced

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.

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: 2 · 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