-
Notifications
You must be signed in to change notification settings - Fork 709
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
OSSFuzz Integration #1245
Open
ennamarie19
wants to merge
5
commits into
jsvine:develop
Choose a base branch
from
ennamarie19:stable
base: develop
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
OSSFuzz Integration #1245
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
Added pipeline Fix path in build script Formatting Add Updated changelog to reflect PR number
Thanks, @ennamarie19. Perhaps I misunderstood, but I was under the impression that fuzzing could be supported in a synced fork (to avoid adding to this repository's infrastructural complexity)?: #1198 (comment) |
I will try the synced fork approach and see if OSS Fuzz approves. I’ll keep you posted. Thank you! On Jan 9, 2025, at 8:44 PM, Jeremy Singer-Vine ***@***.***> wrote:
Thanks, @ennamarie19. Perhaps I misunderstood, but I was under the impression that fuzzing could be supported in a synced fork (to avoid adding to this repository's infrastructural complexity)?: #1198 (comment)
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: ***@***.***>
|
Great, thanks! |
DonggeLiu
pushed a commit
to google/oss-fuzz
that referenced
this pull request
Jan 27, 2025
This pull request integrates the Dockerfile needed to build the fuzzers for pdfplumber. Note: The fuzzers were NOT merged upstream following discussion with the project maintainer [here](jsvine/pdfplumber#1245 (comment)) and with the precedence for out-of-repo fuzzers established [here](#12467) --------- Co-authored-by: bcapuano <[email protected]> Co-authored-by: Bailey Capuano <[email protected]>
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.
Following up on #1198, this PR adds a fuzzing harnesses and a build script to integrate OSS-Fuzz into the project.
Further, this adds the necessary workflow pipeline to automatically fuzz all pull requests into the stable and develop branches. Until this is merged into stable, that specific pipeline will fail (as it must both be merged in here and into Google's respective OSSFuzz repo before builds start succeeding and producing results / uncovering bugs).