Skip to content

Fix panic when using a repeated field as a predefined rule #245

Fix panic when using a repeated field as a predefined rule

Fix panic when using a repeated field as a predefined rule #245

Triggered via pull request September 30, 2024 23:31
Status Failure
Total duration 21s
Artifacts

buf.yaml

on: pull_request
Validate protos
10s
Validate protos
Fit to window
Zoom out
Zoom in

Annotations

10 errors
Validate protos: <input>#L1
Previously present file "buf/validate/expression.proto" was deleted.
Validate protos: <input>#L1
Previously present file "buf/validate/priv/private.proto" was deleted.
Validate protos: buf/validate/validate.proto#L15
File syntax changed from "proto3" to "proto2".
Validate protos: buf/validate/validate.proto#L73
Extension "1160" with name "buf.validate.predefined" on message "google.protobuf.FieldOptions" changed type from "buf.validate.priv.FieldConstraints" to "buf.validate.PredefinedConstraints".
Validate protos: buf/validate/validate.proto#L73
Extension "1160" on message "google.protobuf.FieldOptions" changed name from "buf.validate.priv.field" to "buf.validate.predefined".
Validate protos: buf/validate/validate.proto#L91
Message "Constraint" JSON format support changed from ALLOW to LEGACY_BEST_EFFORT.
Validate protos: buf/validate/validate.proto#L94
Field "1" with name "id" on message "Constraint" changed cardinality from "optional with implicit presence" to "optional with explicit presence".
Validate protos: buf/validate/validate.proto#L94
Field "1" with name "id" on message "Constraint" changed Java string UTF8 validation from "VERIFY" to "NONE".