tree 1359d3849d0a2688dfeaaf9f37a311f52209c1d7
parent 28b807b56e3c526adc5a101d2b233a5759bf05f5
author Damien Neil <dneil@google.com> 1595434220 -0700
committer Damien Neil <dneil@google.com> 1595534940 +0000

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>