-
Notifications
You must be signed in to change notification settings - Fork 606
FEAT Breaking: Adding Resiliency to Scenarios #1164
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
FEAT Breaking: Adding Resiliency to Scenarios #1164
Conversation
|
Question about overall attack design: should AtomicAttack support one or multiple objectives? It may be simpler to flatten what we currently have since the point of the AtomicAttack is to my understanding to correspond to one attack attempt. But an AtomicAttack with several objectives, especially if they aren't closely related. may undermine the purpose of the Scenario (e.g. one AtomicAttack with 20 objectives locking or busywaiting a Scenario with 19 other AtomicAttacks, each with one objective) |
AttackExecutorResultand added a flag so that incomplete results can be returned, even if an exception is raised.