-
Notifications
You must be signed in to change notification settings - Fork 22
feat: comment on threshold should be more alarming #251
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
Conversation
Clarified the impact of increasing anomaly score thresholds on WAF protections and emphasized the importance of maintaining a blocking threshold of 5.
Clarified the implications of increasing the anomaly score threshold and emphasized the importance of keeping the blocking threshold at or below 5.
EsadCetiner
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please do not resolve comments that you haven't properly addressed, if you don't understand my request or disagree with it please speak up instead of marking it as resolved.
Right now your changes are very wordy, and is even confusing in some places.
Co-authored-by: Esad Cetiner <[email protected]>
|
I’ve responded to all your points. I understood from another PR that you - or at least Max - preferred having discussions marked as resolved so you can keep track of progress. I can handle it differently with you if you prefer. I’m now waiting for your feedback on my responses. |
I've tagged you in the comments you haven't addressed, I'm still waiting on them.
Yes, but you only mark a discussion marked as resolved once you are finished with it. Meaning you applied the suggestion, if you disagree with a suggestion or don't understand it you don't mark it as resolved, you ask follow up questions or express your disagreement until an agreement is come to. |
|
I’ve given you detailed explanations about why I disagreed with some points, and the two change requests have been marked as unresolved. I’m now waiting for your feedback. |
|
I don't understand why you don't see it. |
|
@touchweb-vincent You haven't published your review, that's why it says "Pending" in orange above your message. You need to publish your review, you can do that by clicking the files tab and "submit review" at the top right: |
|
I had never seen this GitHub behavior in the past 3 years! Thank you! |
EsadCetiner
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you, I understand your changes much better now. How do these suggestions sound?
Co-authored-by: Esad Cetiner <[email protected]>
Co-authored-by: Esad Cetiner <[email protected]>



Hello,
Just to be consistent with this : https://github.com/coreruleset/coreruleset/pull/4330/files