FuzzPlugin severity #298
Open
FuzzPlugin severity #298
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
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.
Hi, I noticed issues running
--script, that some were outputing fairly useless messages unless-vfor verbose messages was specified.For example, the
titlescript would output a message that thetitlescript generated a message, but not say what the message is.I believe this is due to a logic error in
is_visible, identified in this pull request's changes.Currently in the codebase, all scripts generate results of severity
FuzzPlugin.INFOwhich should be displayed as the hardcodedMIN_VERBOSEis also equal toINFO.