Repository navigation
Reject timestamp truncation before temporal selection - #26
Merged
Merged
Conversation
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.
An ingestion time of 2026-01-01T00:00:00.0000009Z previously normalized to the earlier microsecond cutoff and could be selected as already known. Fractional zero-second offsets can also lose their fraction in the datetime parser.
Reject more than six fractional-second digits, fractions on shortened hour/minute clock forms, and fractional-second UTC offsets before normalization. Keep supported UTC instants and inclusive microsecond cutoffs unchanged. JSON, native CSV and the optional pandas example share the guard; invalid CLI inputs return status 2 before any report is written. Document the stricter main-only input contract and unchanged release assets.
Validation: eight new unittest methods first reproduce the old behavior; all 145 local tests pass with pandas installed. Both committed scalar and rolling bundles verify without regenerating their bytes. Tests cover all observation timestamps, decisions, both CLI input routes and commands, source-file preservation, supported offsets and a record one microsecond after the cutoff. No model-performance or external-adoption claim is added.