You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The protocol buffer JSON spec seems to serialize int64 values to JSON strings, rather than numbers. It seems that serde/prost expect a number though, so if your proto includes an int64 the de-serialization will fail.
Interesting! Do you have a sample proto message with a code snippet that recreates this behaviour? Better yet if it could be a test case we can add to the test suite....
The protocol buffer JSON spec seems to serialize
int64
values to JSON strings, rather than numbers. It seems that serde/prost expect a number though, so if your proto includes anint64
the de-serialization will fail.Error("invalid type: string \"5000\", expected i64", line: 1, column: 200)'
I am not familiar enough with serde/prost to know where the problem lies, but maybe you have some ideas?
I may be running into more of these edge cases be cause the JSON is being serialized by Go code and then I am trying to deserialize in Rust.
The text was updated successfully, but these errors were encountered: