-
Notifications
You must be signed in to change notification settings - Fork 11
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
First conversion sometimes returns array with all zeros. #12
Comments
Thanks for the report, @xgovern Could you provide an example where you're seeing this conversion issue? |
//Code //Console Log |
Node v10.13.0, by the way. What I do is just do a simple conversion at the top import section to avoid the issue. //Code |
Hm, interesting. I haven't been able to replicate it just yet, even with 10.13.0, but I'll run some further tests to see. I seem to recall having an issue with N-API and |
Quick temp fix may be to run "toBufferLE(1n,1); toBufferBE(1n,1);" |
I'm having the same issue. It's reproducible on glitch https://glitch.com/edit/#!/remix/bigint-buffer-bug. Seems to be fine with byte lengths that are multiples of 8 |
Second conversion and on does not seem to have this issue, but the very first conversion, depending on buffer size and number size returns an array with [0,0,0,0,...,0].
The text was updated successfully, but these errors were encountered: