Damien Neil b5523e32b3 all: return less-specific, but more informative wire unmarshal errors ...

When proto.Unmarshal fails, it is almost always due to being passed
input which is not a wire-format message. (A text-format message, a
message with framing left intact, and so forth.) An error like
"variable length integer overflow" can be confusing in this case, since
it implies the problem is the varint rather than the input being
entirely wrong.

Replace all Unmarshal parse errors with "cannot parse invalid
wire-format data".

Change-Id: Id97253bd39ac604e569df71778194f37b3c86c28
Reviewed-on: https://go-review.googlesource.com/c/protobuf/+/244297
Reviewed-by: Joe Tsai <joetsai@google.com>

2020-07-23 20:09:00 +00:00

..

generate-corpus

internal/fuzz: add fuzzers for prototext and protojson packages

2019-12-20 09:02:05 +00:00

generate-protos

cmd/protoc-gen-go: generate package documentation for well-known types

2020-06-22 19:32:21 +00:00

generate-types

all: return less-specific, but more informative wire unmarshal errors

2020-07-23 20:09:00 +00:00

pbdump

testing/protopack: make package publicly available

2020-03-20 18:05:51 +00:00