-
Notifications
You must be signed in to change notification settings - Fork 4
Attack wave samples #263
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
Attack wave samples #263
Conversation
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.
We don't do it in Node.js, but in theory we could delete the samples from memory after reporting? Not sure if worth the extra code. Looks good expect failing test.
..._api/src/main/java/dev/aikido/agent_api/storage/attack_wave_detector/AttackWaveDetector.java
Show resolved
Hide resolved
| return; | ||
| } | ||
|
|
||
| for (Sample sample : samples) { |
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.
Accessing record components via fields 'sample.method' and 'sample.url' is invalid and will cause compilation failure.
Details
🔧 How do I fix it?
Trace execution paths carefully. Ensure precondition checks happen before using values, validate ranges before checking impossible conditions, and don't check for states that the code has already ruled out.
More info - Comment @AikidoSec feedback: [FEEDBACK] to get better review comments in the future.
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
No description provided.