Python(fix): cache boundary resolution to include ns - #776
Merged
Conversation
alexluck-sift
force-pushed
the
al/python/fix-cache-boundary-resolution
branch
from
September 3, 2026 16:02
705867b to
f2a0642
Compare
Contributor
|
Python docs preview: https://sift-stack.github.io/sift/python/pr-776/ Deployed from |
alexluck-sift
marked this pull request as ready for review
September 3, 2026 16:36
ian-sift
reviewed
Sep 3, 2026
ian-sift
approved these changes
Sep 3, 2026
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
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.
datetime, truncating the nanosecond timestamps that getData supports. Every get data produced aUserWarning: Discarding nonzero nanoseconds in conversiononce per channel, and then incorrectly truncated the precision when stored in cache. Bounds are nowpd.Timestamp, andget_data/get_data_as_arrowacceptpd.Timestampbounds that keep their nanoseconds through to the request.to_timestamp_pb, so the export, run, rule and tag paths stop silently flooring to microseconds.