Fix scaledObject always matching when browserVersion is latest in trigger metadata #4348
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
…if the browserVersion in the ScaledObject is set to latest. Signed-off-by: gifflet <guisousa09@hotmail.com>
Signed-off-by: gifflet <guisousa09@hotmail.com>
|
/run-e2e selenium* |
JorTurFer
approved these changes
Mar 9, 2023
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.
It is necessary to check if the browserVersion is defined in the session before validating if the browserVersion in the trigger of the ScaledObject is set to latest. This way, it will avoid matching a ScaledObject whose browserVersion is set to latest in the trigger to sessions that may have browserVersion with different values.
Checklist
Fixes #4347