Fix allmatch issue with preclass bytecode (1.0.1) #825
+54
−51
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
The verdict is being recorded before the preclass bytecode hook meaning that the final verdict may come back as "clean" in allmatch mode, even if the preclass bytecode hook matches something. This commit moves the verdict check to occur AFTER the preclass bytecode hook executes.
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.
The verdict is being recorded before the preclass bytecode hook meaning that the final verdict may come back as "clean" in allmatch mode, even if the preclass bytecode hook matches something.
This commit moves the verdict check to occur AFTER the preclass bytecode hook executes.
This is a backport of #823