fix: round milliseconds instead of truncating #492
+114
−9
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
YuriZmytrakov
force-pushed
the
CAT-1449
branch
3 times, most recently
from
8f528ba to
1855ca0
Compare
jonhealy1
previously approved these changes
Nov 4, 2025
YuriZmytrakov
force-pushed
the
CAT-1449
branch
from
7d7e44f to
974e910
Compare
jonhealy1
approved these changes
Nov 5, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Description:
This PR improves datetime filtering by implementing proper microsecond rounding instead of truncation. Previously, datetime values with 6-digit microsecond precision (e.g., 2023-01-23T08:32:41.024699Z) were being truncated to 3-digit milliseconds (2023-01-23T08:32:41.024Z), which could lead to incorrect filtering results.
PR Checklist:
pre-commit run --all-files)make test)