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
Conversion of string to binary, and then back from binary to string works correctly when both conversions are made using the Data::UUID module. However the binary representation is not compatible with other libraries. When the string
41324657-9abb-401c-8533-745846b948f7
is converted to binary, the command
od -t x1
shows the binary as
57 46 32 41 bb 9a 1c 40 85 33 74 58 46 b9 48 f7
The left portion of the bytes are transformed.
Using the module UUID::Tiny, the od -t x1 output matches the string:
41 32 46 57 9a bb 40 1c 85 33 74 58 46 b9 48 f7
The text was updated successfully, but these errors were encountered:
For what it's worth, I've hit this problem, as well. I also tried Data::UUID against UUID::Tiny, and my investigation found the same results as @ethandbrown's. Notably:
Conversion of string to binary, and then back from binary to string works correctly when both conversions are made using the Data::UUID module. However the binary representation is not compatible with other libraries. When the string
41324657-9abb-401c-8533-745846b948f7
is converted to binary, the command
od -t x1
shows the binary as
57 46 32 41 bb 9a 1c 40 85 33 74 58 46 b9 48 f7
The left portion of the bytes are transformed.
Using the module UUID::Tiny, the od -t x1 output matches the string:
41 32 46 57 9a bb 40 1c 85 33 74 58 46 b9 48 f7
The text was updated successfully, but these errors were encountered: