Uh oh!
There was an error while loading. Please reload this page.
ARROW-7691: [C++] Check non-scalar Flatbuffers fields are not null - #6293
Closed
pitrou wants to merge 2 commits into
Closed
ARROW-7691: [C++] Check non-scalar Flatbuffers fields are not null#6293pitrou wants to merge 2 commits into
pitrou wants to merge 2 commits into
Conversation
pitrou
commented
Feb 3, 2020
MemberAuthor
Uh oh!
There was an error while loading. Please reload this page.
emkornfield
commented
Feb 4, 2020
Contributor
LGTM, 1 minor comment. |
We're discussing whether to make those fields required in the schema definitions (which would make validation automatic by the flatbuffers generated verifier), but in the meantime we can check those fields manually. This should fix a bunch of issues detected by OSS-Fuzz.
pitrouforce-pushed
the
ARROW-7691-check-fb-fields-not-null
branch
from
February 4, 2020 12:50
9e2d323 to
02478a6Comparekszucs pushed a commit
that referenced
this pull request
Feb 7, 2020
We're discussing whether to make those fields required in the schema definitions (which would make validation automatic by the flatbuffers generated verifier), but in the meantime we can check those fields manually. This should fix a bunch of issues detected by OSS-Fuzz. Closes#6293 from pitrou/ARROW-7691-check-fb-fields-not-null and squashes the following commits: 02478a6 <Antoine Pitrou> Use a function rather than a macro e6d3d88 <Antoine Pitrou> ARROW-7691: Check non-scalar Flatbuffers fields are not null Authored-by: Antoine Pitrou <antoine@python.org> Signed-off-by: Antoine Pitrou <antoine@python.org>
This file contains hidden or 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
Sign up for freeto join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
We're discussing whether to make those fields required in the schema definitions (which would make validation automatic by the flatbuffers generated verifier), but in the meantime we can check those fields manually.
This should fix a bunch of issues detected by OSS-Fuzz.