Skip to content

Conversation

@bitterpanda63
Copy link
Member

No description provided.

Copy link
Member

@timokoessler timokoessler left a 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.

@bitterpanda63 bitterpanda63 marked this pull request as ready for review December 4, 2025 00:06
return;
}

for (Sample sample : samples) {

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
Copy link

codecov bot commented Dec 4, 2025

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

@bitterpanda63 bitterpanda63 merged commit 38d0ffc into main Dec 4, 2025
209 checks passed
@bitterpanda63 bitterpanda63 deleted the attack-wave-samples branch December 4, 2025 00:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants