Skip to content
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

Closed
wants to merge 1 commit into from

Conversation

aozturk
Copy link

@aozturk aozturk commented Nov 15, 2024

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

@facebook-github-bot facebook-github-bot added the CLA Signed This label is managed by the Facebook bot. Authors need to sign the CLA before a PR can be reviewed. label Nov 15, 2024
@facebook-github-bot
Copy link
Contributor

This pull request was exported from Phabricator. Differential Revision: D66003722

Copy link

netlify bot commented Nov 15, 2024

Deploy Preview for meta-velox canceled.

Name Link
🔨 Latest commit f85189e
🔍 Latest deploy log https://app.netlify.com/sites/meta-velox/deploys/673cc97e091017000871c195

Copy link
Contributor

@kevinwilfong kevinwilfong left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks!

aozturk pushed a commit to aozturk/velox that referenced this pull request Nov 18, 2024
…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
@facebook-github-bot
Copy link
Contributor

This pull request was exported from Phabricator. Differential Revision: D66003722

aozturk pushed a commit to aozturk/velox that referenced this pull request Nov 18, 2024
…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
@facebook-github-bot
Copy link
Contributor

This pull request was exported from Phabricator. Differential Revision: D66003722

aozturk pushed a commit to aozturk/velox that referenced this pull request Nov 18, 2024
…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
@facebook-github-bot
Copy link
Contributor

This pull request was exported from Phabricator. Differential Revision: D66003722

@aozturk aozturk changed the title Surface clear parsing error for invalid prestopage header misc: Surface clear parsing error for invalid prestopage header Nov 18, 2024
@facebook-github-bot
Copy link
Contributor

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
@facebook-github-bot
Copy link
Contributor

This pull request was exported from Phabricator. Differential Revision: D66003722

@facebook-github-bot
Copy link
Contributor

This pull request has been merged in f5c7e4a.

Copy link

Conbench analyzed the 1 benchmark run on commit f5c7e4ac.

There were no benchmark performance regressions. 🎉

The full Conbench report has more details.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
CLA Signed This label is managed by the Facebook bot. Authors need to sign the CLA before a PR can be reviewed. fb-exported Merged
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants