go data_error ai_generated true

proto: cannot parse invalid wire-format data: illegal tag 0 (wire type 0)

ID: go/protobuf-unmarshal-invalid-wire-type

Also available as: JSON · Markdown · 中文
80%Fix Rate
88%Confidence
0Evidence
2024-03-05First Seen

Version Compatibility

VersionStatusIntroducedDeprecatedNotes
1.x active — — —

Root Cause

The protobuf binary data is corrupted or not in the expected format. This can happen when the data is truncated, sent over a non-binary channel, or when the wrong message type is used for unmarshaling.

generic

中文

protobuf 二进制数据损坏或不是预期的格式。这可能在数据被截断、通过非二进制通道发送或使用错误的消​​息类型进行反序列化时发生。

Workarounds

  1. 90% success 
    // Before unmarshaling, check data length and source
if len(data) == 0 {
    return errors.New("empty data")
}
var msg YourMessage
if err := proto.Unmarshal(data, &msg); err != nil {
    log.Printf("unmarshal failed: %v, data: %x", err, data)
    return err
}
  2. 85% success 
    // If data is JSON, use protojson
var msg YourMessage
if err := protojson.Unmarshal(jsonData, &msg); err != nil {
    log.Fatalf("protojson unmarshal failed: %v", err)
}

Dead Ends

Common approaches that don't work:

  1. 95% fail

    The error is not about buffer size but about invalid data structure; increasing buffer won't fix corrupted data.

  2. 90% fail

    This leads to silent data corruption and unpredictable behavior downstream.