fix(engine): restrict finding feedback #4377
Merged
Conversation
This file contains hidden or 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
1. Findings were previously wrongly fedback to the engine even after an error in converting to events. This issue was resolved. 2. Finding feedbacks in general are now restricted by the engine config being set to single-binary mode (which now logically includes analyze mode).
|
@yanivagman Confirmed this resolves our e2e issues. |
|
/fast-forward |
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.
2. Explain how to test it
tracee-rules shouldn't crash or emit errors when using a signature plugin that relies on signature feedback. The signature will not work.
In analyze the signature will work just as before.