fix: clean matched vars after chained and non-chained rule #3418
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.
what
This PR changes the code behavior: now the engine cleans the
MATCHED_VAR*
variables after chained and non-chained rules too.why
Until now if there was a single (non-chained) rule, and if any of the
MATCHED_VAR*
variable were filled, then the next rule which used them accessed the filled value, even the rule does not usechain
action.references
See issue #3382.
This PR fixes #3382.
other notes
please see commit 5572ac0; I added this change because the first test on Windows was failed. It seems like the argument processing order is non-deterministic, at least it's different on Windows (see the log: the first argument is the last from the
QUERY_STRING
, and the tests were success on all other platforms).