Add contingencies to limit violation detector API. #772
Conversation
This file contains 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
sylvlecl
changed the title
sylvlecl
force-pushed
the
limit-violations-improvements
branch
2 times, most recently
from
a1d8845 to
475a0f8
Compare
Limit violation detectors can now adapt their behaviour to the current contingency. Security analyses should now call the corresponding methods. At the same time, some javadoc is added for for LimitViolation class, and some utilities for limit violations in general Signed-off-by: Sylvain Leclerc <[email protected]>
sylvlecl
force-pushed
the
limit-violations-improvements
branch
from
475a0f8 to
b1bd95e
Compare
sylvlecl
changed the title
Signed-off-by: Sylvain Leclerc <[email protected]>
miovd
approved these changes
Apr 29, 2019
frannicot
pushed a commit
that referenced
this pull request
May 27, 2019
* Add Contingency information to limit violation detector API. Limit violation detectors can now adapt their behaviour to the current contingency. Security analyses should now call the corresponding methods. At the same time, some javadoc is added for for LimitViolation class, and some utilities for limit violations in general * Restore moved classes to ensure smooth transition. Signed-off-by: Sylvain Leclerc <[email protected]> Signed-off-by: frannicot <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Please check if the PR fulfills these requirements (please use
'[x]'to check the checkboxes, or submit the PR and then click the checkboxes)What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
Some documentation and a non-breaking evolution in the API of limit violations detectors.
What is the current behavior? (You can also link to an open issue here)
Limit violation detectors cannot take into account the context in which they operate (on N situation? after a contingency?).
What is the new behavior (if this is a feature change)?
Limit violation detectors may now adapt their behaviour to the specified contingency.
Does this PR introduce a breaking change? (What changes might users need to make in their application due to this PR?)
No, a default behaviour is provided for new methods.