initial Genesis Fuzz Support fuzz_target.py #202
+51
−0
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
|
Hii @YilingQiao Could Team Review This PR as well as can I get maintainer list so I can Add them who get notified above Alerts Thanks |
|
Hi Shivam, Thank you for your PR. I’m not sure if we need this workflow at the moment. Are there other similar repositories using it? Our current priority is to address some urgent bugs. Let me discuss this with others and get back to you. Thank you so much for your time! |
|
Hii |
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.
Introducing foundational fuzzing support for Genesis to help identify and resolve potential issues.
Once merged, I will submit a pull request to the OSS-Fuzz repo to enable fuzzing for this library on Google infrastructure. Any identified bugs will be reported to the Genesis maintainers.
Kindly review the OSS-Fuzz documentation and Bug Disclosure Guidelines before proceeding with the merge.
Thanks