[attack] Attack stage debug logging, little fixes and enhancements - #150
Merged
Conversation
il3241ya
changed the title
il3241ya
approved these changes
May 13, 2026
meaning-0f-life
pushed a commit
to meaning-0f-life/OpenCDA
that referenced
this pull request
Jul 25, 2026
…AVISE#150) * [attack] Add logging in attack stages * fix capability docstring * better trajectory debuging in aim_client * fix ddos attack config
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Summary
Adds DEBUG-level logging for adversary framework attack stages, making it possible to inspect how each stage changes service capability outputs during attack execution. Also updates the AIM server request DDoS config and includes small cleanup/debug-visualization fixes.
Related issue
Closes #
Changes
log_stage_object_transitionhelper for DEBUG logs with stage name, action, service type, capability, and before/after object state.dropper,replayer,sniffer, andspooferstages.aim_server_request_ddosconfig to start once requirements are met and avoid stopping when tracked vehicle count returns to zero.Capabilitydoc-string typo and raised AIM client trajectory debug points above the ground for clearer visualization.Validation
Checklist