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
Timestamps are encoded as 64bit integers but are here decoded as two 32 bit numbers. Normally this works well when the timestamp is a 32bit number, but not when it has millisecond precision.
## Changes between 2.1.0 and 2.2.0 (unreleased)
### Timestamps are Encoded as 64-bit Unsigned Integers
This is a potentially **breaking change**. It is recommended that
all applications that use this gem and pass date/time values in message
properties or headers are upgraded at the same time.
GitHub issue: [#64](ruby-amqp/amq-protocol#64).
Contributed by Carl Hoerberg.
Timestamps are encoded as 64bit integers but are here decoded as two 32 bit numbers. Normally this works well when the timestamp is a 32bit number, but not when it has millisecond precision.
At
amq-protocol/lib/amq/protocol/table_value_decoder.rb
Line 135 in dd48b32
instead of
we should do
And at encoding:
amq-protocol/lib/amq/pack.rb
Line 9 in c292d82
To do big-endian (network-endian) encoding and not platform/native endian.
The text was updated successfully, but these errors were encountered: