Recordsgolanggoogle.golang.org/protobuffailure issue
Failure signature
UNKNOWN exit 1 Evidence gap ×1
FAIL: expected error when marshaling untyped nil proto.Message · exit status 1
Evidence quality: complete · go · unclassified-diagnostic · outer go run · gap stage-unknown · First recorded: 2026-08-29 · Last seen: 2026-08-29
sha256:5684c2833557…
google.golang.org/protobuf/proto.Equal google.golang.org/protobuf/proto.Marshal google.golang.org/protobuf/proto.MarshalOptions google.golang.org/protobuf/proto.Size google.golang.org/protobuf/proto.Unmarshal google.golang.org/protobuf/types/known/emptypb.Empty google.golang.org/protobuf/types/known/structpb.NewStruct google.golang.org/protobuf/types/known/timestamppb.New google.golang.org/protobuf/types/known/wrapperspb.Int32 google.golang.org/protobuf/types/known/wrapperspb.String google.golang.org/protobuf/types/known/wrapperspb.StringValue
Where it was measured
PASS means the release recorded a passing observation at UNKNOWN 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
- os=linux · runtime=go@1.26 ×1 2026-08-29 → 2026-08-29
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.
| Library | v1.36.12 | v1.36.11 | v1.36.10 |
|---|---|---|---|
| github.com/golang/protobuf | v1.5.2 | v1.5.3 | v1.5.0 |
| github.com/google/go-cmp | v0.7.0 | v0.7.0 | v0.7.0 |
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
- The evidence for this failure was not preserved, so it has no established cause. Its stored hash is provenance, not an identity.
- The captured output could not establish: stage-unknown.
- No release in this window recorded a passing observation at UNKNOWN.
- Releases in this window never measured at UNKNOWN: 3
- No failure domain was inferred for this failure.
Published answers for the affected releases
- google.golang.org/protobuf v1.36.12: Merge, clone, equality, and reset semantics for Protocol Buffers messages across presence types, repeated slices, maps, and floating-point values 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. HOWgoogle.golang.org/protobuf/proto.Mergegoogle.golang.org/protobuf/proto.Equalgoogle.golang.org/protobuf/proto.Clonegoogle.golang.org/protobuf/proto.Resetgoogle.golang.org/protobuf/reflect/protoreflect.Message.Hasgo MIT-0 · 2026-08-17
- google.golang.org/protobuf v1.36.12: Control JSON formatting and parsing of Protocol Buffers messages using protojson MarshalOptions and UnmarshalOptions 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. HOWgoogle.golang.org/protobuf/encoding/protojson.Marshalgoogle.golang.org/protobuf/encoding/protojson.MarshalOptionsgoogle.golang.org/protobuf/encoding/protojson.Unmarshalgoogle.golang.org/protobuf/encoding/protojson.UnmarshalOptionsgo MIT-0 · 2026-08-17