Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

SET with EX with big integer reports an error #563

Merged

Conversation

nithinkjoy-tech
Copy link
Contributor

@nithinkjoy-tech nithinkjoy-tech commented Sep 12, 2024

Closes #511

Passes TCL Test
Screenshot 2024-09-12 at 11 06 51 PM

Passes existing dice tests
Screenshot 2024-09-12 at 11 09 09 PM

Working Example. (Changed port number to 6379 locally for running server)
Screenshot 2024-09-12 at 11 20 25 PM

@arpitbbhayani
Copy link
Contributor

Patch looks good. @nithinkjoy-tech thanks a ton. merging it.

@arpitbbhayani arpitbbhayani merged commit 97d3cd5 into DiceDB:master Sep 13, 2024
2 checks passed
@arpitbbhayani arpitbbhayani self-requested a review September 13, 2024 11:41
@AshwinKul28
Copy link
Contributor

Thanks @nithinkjoy-tech for the fix, this will work for most of the cases, but the precise value as follows.

The max value redis supports is based on the maximum signed 64-bit integer (int64) which is 9223372036854775807. Since redis accepts it in milliseconds the max value would be 9223372036854775 milliseconds, which corresponds to maximum duration that Redis can represent before exceeding the range of a signed 64-bit integer. I will fix this in the next PR.

cc - @arpitbbhayani .

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Inconsistent SET: SET with EX with big integer should report an error
3 participants