protobuffer inconsistency

[joticajulian]

Let's say we have the following proto:

message test {
   uint64 a = 1 [jstype = JS_STRING];
   repeated uint64 b = 2 [jstype = JS_STRING];
}

and we want to encode the message

{a: 10, b: [54, 55, 56]}

koilib (protobuffers.js) encodes it as:

hex value: 08 0a 12 03 36 37 38

However, as-proto encodes it as:

hex value: 08 0a 10 36 10 37 10 38

This inconsistency makes the contracts exit with transaction reverted: module exited due to trap because as-proto is not able to decode the data created in koilib.

By looking to the documentation it seems that as-proto is using the correct encoding https://protobuf.dev/programming-guides/encoding/#optional.

Verify this and report the issue to the corresponding library.

[joticajulian]

Note: This issue is solved by using a nested message in the repeated field.

Example:

message mynumber {
   uint64 value = 1 [jstype = JS_STRING];
}

message test {
   uint64 a = 1 [jstype = JS_STRING];
   repeated mynumber b = 2;
}