-
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
misc: Surface clear parsing error for invalid prestopage header #11552
Conversation
This pull request was exported from Phabricator. Differential Revision: D66003722 |
✅ Deploy Preview for meta-velox canceled.
|
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!
c724ac5
to
07cfd2b
Compare
…bookincubator#11552) Summary: During deserialization, PrestoPage header is parsed with the assumption of enough bytes in the provided input stream. This causes exceptions that are not easy to interpret when there is invalid data provided. This change validates existence of enough bytes before parsing the header and surfaces the parsing error with a clear exception message. Reviewed By: kevinwilfong Differential Revision: D66003722
This pull request was exported from Phabricator. Differential Revision: D66003722 |
…bookincubator#11552) Summary: During deserialization, PrestoPage header is parsed with the assumption of enough bytes in the provided input stream. This causes exceptions that are not easy to interpret when there is invalid data provided. This change validates existence of enough bytes before parsing the header and surfaces the parsing error with a clear exception message. Reviewed By: kevinwilfong Differential Revision: D66003722
07cfd2b
to
3584bc3
Compare
This pull request was exported from Phabricator. Differential Revision: D66003722 |
…bookincubator#11552) Summary: During deserialization, PrestoPage header is parsed with the assumption of enough bytes in the provided input stream. This causes exceptions that are not easy to interpret when there is invalid data provided. This change validates existence of enough bytes before parsing the header and surfaces the parsing error with a clear exception message. Reviewed By: kevinwilfong Differential Revision: D66003722
3584bc3
to
e8d3252
Compare
This pull request was exported from Phabricator. Differential Revision: D66003722 |
This pull request was exported from Phabricator. Differential Revision: D66003722 |
…bookincubator#11552) Summary: During deserialization, PrestoPage header is parsed with the assumption of enough bytes in the provided input stream. This causes exceptions that are not easy to interpret when there is invalid data provided. This change validates existence of enough bytes before parsing the header and surfaces the parsing error with a clear exception message. Reviewed By: kevinwilfong Differential Revision: D66003722
e8d3252
to
f85189e
Compare
This pull request was exported from Phabricator. Differential Revision: D66003722 |
This pull request has been merged in f5c7e4a. |
Conbench analyzed the 1 benchmark run on commit There were no benchmark performance regressions. 🎉 The full Conbench report has more details. |
Summary: During deserialization, PrestoPage header is parsed with the assumption of enough bytes in the provided input stream. This causes exceptions that are not easy to interpret when there is invalid data provided. This change validates existence of enough bytes before parsing the header and surfaces the parsing error with a clear exception message.
Differential Revision: D66003722