Repository navigation
fix: preserve nanosecond execution and replay timestamps - #26
Merged
Merged
Conversation
This was referenced Oct 8, 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
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.
Preserve nanosecond timestamps across JSON decoding, streamed order recovery, dividend replay, corporate-action posting and US cash cutoffs. The shared parser rejects finer-than-nanosecond input; ordinary microsecond JSON decoding retains its previous datetime representation.
Pin QDK to the reviewed PR #34 candidate 61b571bdb9bba5d0a8c3aff8b406864539d0a9fc. Merge after PureSaber/quant-data-kit#34.
Validation: Windows/Python 3.12, 372 tests passed, total coverage 94.73%; all ten existing core pure-branch gates remain above 90%; Ruff and format checks passed. Eleven added precision regressions cover exact boundaries, future-fact rejection, JSON/stream recovery, replay hashes and account timing. The prior code failed ten of these eleven cases with the new QDK candidate. Existing golden records and deterministic replay tests pass unchanged.