Protobuf encoding & decoding not compatible with different references

[AYAHASSAN287]

Problem

proc decodeRpcMsg() and encodeRpcMsg don't behave as protocol buffer behaves

Impact

encoding & decoding might be wrong

To reproduce

1-call encodeRpcMsg(rpcmsg) where rpmsg=(
control: some(
ControlMessage(
ihave: @[ControlIHave(topicID: "foobar", messageIDs: @[id])],
iwant: @[ControlIWant(messageIDs: @[id])],
graft: @[ControlGraft(topicID: "foobar")],
prune: @[ControlPrune(topicID: "foobar", backoff: backofftime)],
idontwant: @[ControlIWant(messageIDs: @[id])],
)
)
)

2-encode the same message using protocbuf cmd tool version "libprotoc 3.21.12"
command in terminal " cat data.txt |protoc --deterministic_output --encode=RPC schema.proto > result.bin "
data.txt contains rpcmsg
schema.proto contains the schema defined in the spec here

Expected behavior

encoded message should = expectedmsg generated from protoc cmd line tool.

Screenshots/logs

.

version/commit hash

branch master
commit:5d48776b0250741b10c3ed7df7a61f3f315b96fe

addiitonal notes

protobuf used in python with same message format and the result was same one generated from protoc cmd tool

[AlejandroCabeza]

I'd encourage using the three backticks ``` at the beginning and end of a codeblock. Makes reading it much easier :)

[AlbertoSoutullo]

I just saw this by mere coincidence, and I think this might help :)

https://protobuf.dev/programming-guides/serialization-not-canonical/