Avoid 32-bit integer overflow after 2038 #444
Closed
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
after 2038-01-19, a 32-bit signed int is no more sufficient to hold UNIX epoch timestamp values and will overflow to minus 2 billion. Fixes theimpossibleastronaut#439
andy5995
added a commit
that referenced
this pull request
Mar 26, 2024
Co-authored-by: Bernhard M. Wiedemann <[email protected]> Closes #444
andy5995
added a commit
that referenced
this pull request
Mar 26, 2024
Co-authored-by: Bernhard M. Wiedemann <[email protected]> Closes #444
Closed
|
Completed in #442 |
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.
after 2038-01-19, a 32-bit signed int is no more sufficient
to hold UNIX epoch timestamp values and will overflow to
minus 2 billion.
Fixes #439