Repository navigation
Prevent numeric timestamp strings from being parsed as calendar dates - #1549
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
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.
Numeric timestamp strings such as
"72420101.0625"can be accepted as compact ISO dates, silently changing their value and causing time-window queries to miss edges.Parse numeric strings before ISO dates. Keep ISO/UTC support and align the legacy invalid-input test with the existing
ParsingErrorcontract.Validation: 3 new regressions fail on the base revision; all 233 temporal, streaming, and property tests pass with the fix.
CI caveat: existing workflows suppress pytest failures; the focused validation above was run directly.