Repository navigation
Reject UTC timestamp overflow before building reports - #12
Merged
Merged
Conversation
dev-belly
marked this pull request as ready for review
October 11, 2026 04:01
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
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.
ISO timestamps near the supported year boundaries can overflow when their UTC offset is applied. Previously the API raised OverflowError and build/aggregate escaped the CLI error handler. Normalize that condition to a contract ValueError before creating output files; representable boundary timestamps remain accepted.
Validation: the overflow regressions fail on the baseline, then all 91 tests pass after the fix. New coverage checks both UTC endpoints and build/aggregate error code 2 with no output directory.