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
Given that the test clears internally when you parse back in, I have a feeling that the library maybe doesn't implement the spec correctly. This is backed up by rmp and rmp_serde parsing cleanly with the tools.
The rmp-serde.mp file starts with a byte 0x93. According to the spec, this is a fixed array delimiter with 3 elements (name, inhabitants_per_street, and zones). It seems these other tools expect the payload to start with either an array, map, or otherwise exclusively contain a single messagepack type -- opposed to this library's list of types with no outer container at the top level
The text was updated successfully, but these errors were encountered:
I checked out another person's branch, from PR #16 . It solves the nightly compilation issues, and completes without a problem.
However, writing out the payload, and checking it with external tools, I encountered some errors.
Given that the test clears internally when you parse back in, I have a feeling that the library maybe doesn't implement the spec correctly. This is backed up by
rmp
andrmp_serde
parsing cleanly with the tools.Here's the difference in the hex:
The
rmp-serde.mp
file starts with a byte0x93
. According to the spec, this is a fixed array delimiter with 3 elements (name, inhabitants_per_street, and zones). It seems these other tools expect the payload to start with either an array, map, or otherwise exclusively contain a single messagepack type -- opposed to this library's list of types with no outer container at the top levelThe text was updated successfully, but these errors were encountered: