fix: reject timestamps outside 32-bit ObjectID range#115
Open
leno23 wants to merge 1 commit into
Open
Conversation
Fixes rs#107 by validating Unix seconds in NewWithTimeE instead of silently truncating. NewWithTime panics on out-of-range times, matching other fatal misconfiguration paths in the package.
7d1891d to
6ad82eb
Compare
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
1 participant
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.
Summary
Fixes #107
NewWithTimepreviously castt.Unix()touint32, so times beyond2^32-1seconds (or before the Unix epoch) produced IDs whoseTime()did not round-trip.NewWithTimeEreturningErrTimestampOutOfRangewhent.Unix()is out of rangeNewWithTimedelegates toNewWithTimeEand panics on error (same style as other fatal misconfiguration in this package)Test plan
go test ./...maxTimestamp, error on overflow and negative times