-
Notifications
You must be signed in to change notification settings - Fork 464
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
fix: TypeError in fuzzing reports of fuzz_renv_lock #4052
Comments
On further investigation, it seems the |
I am working on this |
I'm not sure what you needed me to approve here? Did you mean you were waiting for me to tag it or something? I'm confused. |
Yes like whenever I file a new issue I always kind of wait for you to look at it once. Just in case I'm wrong somewhere. |
hah, that is terrible practice for open source in general. As an issue filer, you get to be your own source of truth! Own it! Own the possibility being wrong on the internet sometimes! (It happens to all of us, and the effort involved in saying "whoops" and closing a bug is pretty minimal.) You can actually choose tags by using the issue templates. If you think it's helpful to have a set template for fuzzing issues (which it probably would be?) you can make a PR to create what you need. The existing templates are in this directory: https://github.com/intel/cve-bin-tool/tree/main/.github/ISSUE_TEMPLATE . For now, you can actually use the docstrings issue template, erase everything in it, and you'll still get the "good first issue" tag. |
Thank you for sharing this knowledge with me. |
Related #4045
Issue related to error related to the most recent run of the fuzzers in https://github.com/intel/cve-bin-tool/actions/runs/8684795394
The text was updated successfully, but these errors were encountered: