-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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-6362): cache cursor deserialization options across deserialize calls #4221
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
baileympearson
force-pushed
the
fix-regress
branch
from
September 4, 2024 19:55
b3c6494
to
a5ddeb9
Compare
baileympearson
changed the title
feat(NODE-6309): Mark range API as stable (#4190)
fix(todo-xxxxx): cache cursor deserialization options across deserialize calls (#4190)
Sep 5, 2024
baileympearson
force-pushed
the
fix-regress
branch
3 times, most recently
from
September 6, 2024 16:32
a598416
to
5e9bbc2
Compare
baileympearson
changed the title
fix(todo-xxxxx): cache cursor deserialization options across deserialize calls (#4190)
fix(NODE-6362): cache cursor deserialization options across deserialize calls (#4190)
Sep 6, 2024
baileympearson
force-pushed
the
fix-regress
branch
from
September 9, 2024 14:30
3880d93
to
fb8390f
Compare
nbbeeken
added
the
Primary Review
In Review with primary reviewer, not yet ready for team's eyes
label
Sep 9, 2024
nbbeeken
requested changes
Sep 9, 2024
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.
quick fixes
test/integration/node-specific/bson-options/utf8_validation.test.ts
Outdated
Show resolved
Hide resolved
nbbeeken
changed the title
fix(NODE-6362): cache cursor deserialization options across deserialize calls (#4190)
fix(NODE-6362): cache cursor deserialization options across deserialize calls
Sep 9, 2024
nbbeeken
approved these changes
Sep 9, 2024
This was referenced Oct 3, 2024
This was referenced Oct 5, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
What is changing?
Forward-port of #4220.
Is there new documentation needed for these changes?
What is the motivation for this change?
Release Highlight
Fixed
enableUtf8Validation
optionStarting in v6.8.0 we inadvertently removed the ability to disable UTF-8 validation when deserializing BSON. Validation is normally a good thing, but it was always meant to be configurable and the recent Node.js runtime issues (v22.7.0) make this option indispensable for avoiding errors from mistakenly generated invalid UTF-8 bytes.
Double check the following
npm run check:lint
scripttype(NODE-xxxx)[!]: description
feat(NODE-1234)!: rewriting everything in coffeescript