-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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(json_parse): Tape failure due to out of bounds ':' #11831
base: main
Are you sure you want to change the base?
Conversation
✅ Deploy Preview for meta-velox canceled.
|
9f42aa6
to
8b48b9f
Compare
This pull request was exported from Phabricator. Differential Revision: D67108827 |
This pull request was exported from Phabricator. Differential Revision: D67108827 |
Summary: SIMDJSON fails with a tape failure when if a ':' immediately follows the end of a \" when parsing even though ':' is outside the range of the input. This can happen if the previous string had a ':' at just the right location as we dont clear the buffer when processing strings. Fixes T210222818 . Differential Revision: D67108827
8b48b9f
to
7b9ec81
Compare
This pull request was exported from Phabricator. Differential Revision: D67108827 |
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 @kgpai for fixing it so quickly!
Summary: SIMDJSON fails with a tape failure when if a ':' immediately follows the end of a \" when parsing even though ':' is outside the range of the input. This can happen if the previous string had a ':' at just the right location as we dont clear the buffer when processing strings. Fixes T210222818 . Reviewed By: amitkdutta Differential Revision: D67108827
7b9ec81
to
b8c0cfa
Compare
This pull request was exported from Phabricator. Differential Revision: D67108827 |
Summary: SIMDJSON fails with a tape failure when if a ':' immediately follows the end of a " when parsing even though ':' is outside the range of the input. This can happen if the previous string had a ':' at just the right location as we dont clear the buffer when processing strings. Fixes T210222818 .
Differential Revision: D67108827