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

year 2038 overflow problem #4

Open
elio-bteich opened this issue May 24, 2022 · 0 comments
Open

year 2038 overflow problem #4

elio-bteich opened this issue May 24, 2022 · 0 comments

Comments

@elio-bteich
Copy link

elio-bteich commented May 24, 2022

You've said that we will have a problem with the overflow in 2038 since everyone is declaring timestamps as 32 bytes integers but if we calculate 2^32 -1 = 4,294,967,295 which is the max integer represented on 32 bytes, this number represents in Unix Timestamp Feb 07 2106 and not year 2038, so the overflow will happen on February 2106.

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

No branches or pull requests

1 participant