rules: disable TRC-1022 #2304
Merged
rules: disable TRC-1022 #2304
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
|
@josedonizetti you need to remove from the test list as well I suppose. |
This signatures is triggering way too many times for any new pod deployed to a kubernetes cluster.
josedonizetti
force-pushed
the
disable-TRC-1022
branch
from
e23dd64
to
aa22c9a
Compare
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.
disable TRC-1022, new executable dropped, because it is triggering thousands of false positives on a kubernetes cluster every time a new pod is created.
I'll create an issue to investigate this further before we reenable it.
@roikol ^^