Recordsgolanggoogle.golang.org/protobuffailure issue
Failure signature
UNKNOWN exit 1 Evidence gap ×1
panic: Expected indented JSON · goroutine 1 [running]: · main.main() · <path>:<n> +0x10c7
Evidence quality: complete · go · unclassified-diagnostic · outer go run · gap stage-unknown · First recorded: 2026-08-30 · Last seen: 2026-08-30
sha256:1bdc7cc81d54…
google.golang.org/protobuf/encoding/protojson.Marshal google.golang.org/protobuf/encoding/protojson.MarshalOptions google.golang.org/protobuf/encoding/protojson.Unmarshal google.golang.org/protobuf/encoding/protojson.UnmarshalOptions google.golang.org/protobuf/proto.Equal google.golang.org/protobuf/proto.MarshalOptions google.golang.org/protobuf/proto.Size google.golang.org/protobuf/types/known/anypb.Any google.golang.org/protobuf/types/known/anypb.New google.golang.org/protobuf/types/known/durationpb.New google.golang.org/protobuf/types/known/fieldmaskpb.FieldMask google.golang.org/protobuf/types/known/structpb.NewStruct google.golang.org/protobuf/types/known/structpb.Struct google.golang.org/protobuf/types/known/timestamppb.New google.golang.org/protobuf/types/known/wrapperspb.String
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.
- v1.36.12 not measured
- v1.36.11 not measured
- v1.36.10 FAIL
- v1.36.8 not measured
- v1.36.6 not measured
- v1.36.5 not measured
Where it reproduced
- os=linux · runtime=go@1.26 ×1 2026-08-30 → 2026-08-30
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 | v1.36.6 | v1.36.5 |
|---|---|---|---|---|---|
| github.com/golang/protobuf | v1.5.2 | v1.5.0 | v1.5.0 | v1.5.0 | v1.5.4 |
| github.com/google/go-cmp | v0.7.0 | v0.7.0 | v0.7.0 | v0.5.5 | v0.6.0 |
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
- 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: 5
- No failure domain was inferred for this failure.
Published answers for the affected releases
- google.golang.org/protobuf v1.36.10: protojson.MarshalOptions 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. HOWprotojson.MarshalOptionsgo MIT-0 · 2026-09-02
- google.golang.org/protobuf v1.36.10: protojson.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. HOWprotojson.UnmarshalOptionsgo MIT-0 · 2026-09-02
- google.golang.org/protobuf v1.36.10 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. HOW MIT-0 · 2026-08-27