-
-
Notifications
You must be signed in to change notification settings - Fork 77
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Handle int64 #17
Comments
(First, thanks for your work on this project!) I need int64 support and I think using that library is fine. The current way that msgpack5 encodes int64 is not to spec (as of 2.0.0):
Expected:
I ran into this problem trying to interoperate this library with https://github.com/msgpack/msgpack-javascript (probably problematic anyway besides this problem due to how dated the other project is). I think even if approximate 64-bit values were used, the encoding of the approximate value should match that of the specification. |
Thanks for reporting! Can you please send a PR to address this problem? |
Wanted to check in and see if there is a fix for this. I found the same problem and fixed the byte order and offset issue but not using the library, just the javascript int representation. If you think the fix using the library is coming I'll wait for it, otherwise I'm happy to submit my fix. |
This should be already released.
|
@mcollina Just tried using this library for objects containing int64 and it doesn't seem to work. For example: console.log(encode(0xffffffffffffffff))
<Buffer cb 43 f0 00 00 00 00 00 00> I would expect the buffer to be:
|
If you reopen this issue I could submit a PR to add support for |
Feel free to open an new issue, this one is very old. |
Opened #61 |
Currently we do not support int64. I think we should do that using https://github.com/broofa/node-int64.
Any opinions?
The text was updated successfully, but these errors were encountered: