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
I hit an issue a few days ago with the fact that the MessageBufferPacker's packInt method (and other pack methods ) pack a number to take as little space on the wire as possible (So your i32 could be serialized as a u16, a u8,i8, etc) . This caused an issue with another library that was type sensitive.
I hit an issue a few days ago with the fact that the MessageBufferPacker's
packInt
method (and other pack methods ) pack a number to take as little space on the wire as possible (So your i32 could be serialized as a u16, a u8,i8, etc) . This caused an issue with another library that was type sensitive.While this is a reasonable implementation, the documentation here
https://static.javadoc.io/org.msgpack/msgpack-core/0.8.2/org/msgpack/core/MessagePacker.html
Should mention that
packInt
,packByte
, etc do not guarantee the binary header of that typeThe text was updated successfully, but these errors were encountered: