Fix newTimestampFromTime panic on extreme dates (closes #15) #20

Merged

sneak merged 2 commits from fix/issue-15 into next 2026-02-09 02:10:21 +01:00

Conversation 0 Commits 2 Files Changed 2 +25 -3

clawbot commented 2026-02-08 21:06:23 +01:00

Collaborator

Copy Link

No description provided.

sneak was assigned by clawbot 2026-02-08 21:06:23 +01:00

clawbot added 1 commit 2026-02-08 21:06:24 +01:00

fix: use Nanosecond() instead of UnixNano() in newTimestampFromTime to prevent panic ... ac25e0638c

time.UnixNano() panics for dates outside ~1678-2262. The Nanosecond()
method returns just the nanosecond component (0-999999999) and is safe
for all dates. This matches the pattern already used in ModTime.Timestamp().

sneak added 1 commit 2026-02-09 02:09:58 +01:00

Merge branch 'next' into fix/issue-15 957ef69e26

sneak merged commit 70af055d4e into next 2026-02-09 02:10:21 +01:00

sneak referenced this issue from a commit 2026-02-09 02:10:23 +01:00

Fix newTimestampFromTime panic on extreme dates (closes #15) (#20)

clawbot referenced this pull request 2026-02-09 02:16:43 +01:00

Add deterministic file ordering in Builder.Build() (closes #23) #28

Sign in to join this conversation.

Reviewers

No reviewers

Labels

Clear labels

No items

No Label

Milestone

Clear milestone

No items

No Milestone

Assignees

Clear assignees

No Assignees

sneak

2 Participants

Notifications

Subscribe

Due Date

The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: sneak/mfer#20

No description provided.