Uh oh!
There was an error while loading.Please reload this page.
- Notifications
You must be signed in to change notification settings - Fork960
Fuzzing: Fix Broken Fuzz Test for Git Submodule Handling#1997
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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
Fuzzing: Fix Broken Fuzz Test for Git Submodule Handling#1997
Uh oh!
There was an error while loading.Please reload this page.
Conversation
Ensured submodule names, paths, and commit messages are sanitized toavoid invalid states that are expected to cause exceptions and shouldnot halt the fuzzer.In particular, the changes here:- Sanitized inputs for submodule names, paths, and commit messages.- Added validation for submodule SHA and path integrity.
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 for your continued support with this, it's much appreciated!
583c011 intogitpython-developers:mainUh oh!
There was an error while loading.Please reload this page.
This worked. Issue now resolved on the OSS-Fuzz tracker:https://issues.oss-fuzz.com/379326001 |
Hey there 👋
As you may or may not have seen, the
fuzz_submodule.pyharness has been failing for some time now and I believe it is responisble for the "fuzzing build: failing" status on OSS-Fuzz.I looked into it and it appears to be an issue with the test implementation, not GitPython.
The changes here should fix the issue causing the failure!
Please see the commit message for additional details.