fix: preserve record clock precision in changes - #373
Merged
WaylandYang merged 3 commits intoSep 5, 2026
Conversation
Signed-off-by: danwood <118035379+Floating-Y@users.noreply.github.com>
Signed-off-by: WaylandYang <wayland0916@gmail.com>
This was referenced Sep 5, 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
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.
Summary
Fixes #351.
changesvalidrange at date precisionentity_factsone microsecond before a correction timestamp when it needs the preceding stateWhy
Rounding a record timestamp to a day made it impossible to reliably reconstruct the state before a correction. Subtracting a whole day or second could skip earlier records; at the correction timestamp, the new fact already applies.
Validation
cargo test --workspacecargo clippy --workspace --all-targets -- -D warningspnpm build