-
Notifications
You must be signed in to change notification settings - Fork 256
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
fix(NODE-6764): incorrect negative bigint handling #752
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the quick fix! The change looks good to me, and should fix the issue I had
test/node/bigint.test.ts
Outdated
@@ -105,6 +105,39 @@ describe('BSON BigInt support', function () { | |||
|
|||
it(description, test); | |||
} | |||
|
|||
describe('edge case tests', function () { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just a little nit. Instead of just calling these edge case tests can we better describe what we are testing here? I'd personally prefer individual it
blocks with specific descriptions than the generic describe and loop.
Description
Correct regression to bigint deserialziation introduced in #649
What is changing?
Is there new documentation needed for these changes?
What is the motivation for this change?
Release Highlight
useBigInt64
is enabledAfter refactoring to improve deserialization performance in #649, we inadvertently introduced a bug that manifested when deserializing
Long
values with theuseBigInt64
flag enabled. The bug would lead to negativeLong
values being deserialized as unsigned integers. This issue has been resolved here.Thanks to @rkistner for reporting this bug!
Double check the following
npm run check:lint
scripttype(NODE-xxxx)[!]: description
feat(NODE-1234)!: rewriting everything in coffeescript