Fix wrong sensitive access assignment #125
Open
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
lfv89
commented
Oct 1, 2024
| @@ -33,7 +33,13 @@ def before_executing(statements) | |||
| end | |||
| end | |||
|
|
|||
| def after_executing(statements) | |||
There was a problem hiding this comment.
The method was already hanging in place, so I took advantage by applying the fix there.
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.
This PR aims to fix some sensitive access inconsistencies. The main issue being that after a tempering attempt was made in protected mode, every following command was also being flagged as sensitive (suspicious), even the legitimate ones, which of course is not the expected behavior.
Before:
After: