-
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-3627): Enable flexible BSON validation for server error key containing invalid utf-8 #3054
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
…containing invalid utf8
…est, remove .only
durran
added
the
Primary Review
In Review with primary reviewer, not yet ready for team's eyes
label
Nov 23, 2021
durran
requested changes
Nov 23, 2021
durran
previously approved these changes
Nov 24, 2021
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.
Nice work, thanks!
gjchong25
changed the title
feat(NODE-3627): Enable flexible BSON validation for server error key containing invalid utf-8
fix(NODE-3627): Enable flexible BSON validation for server error key containing invalid utf-8
Nov 24, 2021
…ONSerializeOptions and options registry
durran
added
Team Review
Needs review from team
and removed
Primary Review
In Review with primary reviewer, not yet ready for team's eyes
labels
Nov 29, 2021
dariakp
requested changes
Nov 29, 2021
dariakp
approved these changes
Nov 30, 2021
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 @gjchong25 and @nbbeeken both!
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
This change allows for validation toggling on the
writeErrors
key, which can contain a server error message which has invalid utf-8, thus causing the user to get an invalid utf-8 error rather than the corresponding server error. Unit tests using a real server error response are added to make sure the invalid utf-8 error is not being thrown when validation on thewriteErrors
key is turned off.Double check the following
npm run check:lint
script<type>(NODE-xxxx)<!>: <description>