Add tests to cover EXPIRE overflow detection fix#9839
Merged
oranagra merged 1 commit intoredis:unstablefrom Nov 24, 2021
Merged
Add tests to cover EXPIRE overflow detection fix#9839oranagra merged 1 commit intoredis:unstablefrom
oranagra merged 1 commit intoredis:unstablefrom
Conversation
In redis#8287, some overflow checks have been added. But when `when *= 1000` overflows, it will become a positive number. And the check not able to catch it. The key will be added with a short expiration time and will deleted a few seconds later. In redis#9601, will check the overflow after `*=` and return an error first, and avoiding this situation. In this commit, added some tests to cover those code paths. Found it in redis#9825, and close it.
oranagra
changed the title
oranagra
added
the
release-notes
Member
|
@enjoy-binbin did you verify that this test fails on the code before the fix (v6.2)? |
Contributor
Author
|
Actually only this My words is a bit unclear, In old code, if |
Member
|
ok, great, i assumed only one of them is the one who fails on 6.2, but it's good you added all of them. |
oranagra
approved these changes
Nov 24, 2021
hwware
pushed a commit
to hwware/redis
that referenced
this pull request
Dec 20, 2021
In redis#8287, some overflow checks have been added. But when `when *= 1000` overflows, it will become a positive number. And the check not able to catch it. The key will be added with a short expiration time and will deleted a few seconds later. In redis#9601, will check the overflow after `*=` and return an error first, and avoiding this situation. In this commit, added some tests to cover those code paths. Found it in redis#9825, and close it.
oranagra
added
the
breaking-change
oranagra
pushed a commit
that referenced
this pull request
Apr 27, 2022
In #8287, some overflow checks have been added. But when `when *= 1000` overflows, it will become a positive number. And the check not able to catch it. The key will be added with a short expiration time and will deleted a few seconds later. In #9601, will check the overflow after `*=` and return an error first, and avoiding this situation. In this commit, added some tests to cover those code paths. Found it in #9825, and close it. (cherry picked from commit 9273d09)
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
In #8287, some overflow checks have been added. But when
when *= 1000overflows, it will become a positive number.And the check not able to catch it. The key will be added with
a short expiration time and will deleted a few seconds later.
In #9601, will check the overflow after
*=and return anerror first, and avoiding this situation.
In this commit, added some tests to cover those code paths.
Found it in #9825, and close it.