You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 08bcce9
Browse filesBrowse the repository at this point in the historyBrowse files
Truncating at the write path fixes the live break, but leaves the invariant
as a convention: a future write path that stamps `created_at` without
`to_storage_precision` reintroduces the write/read preimage split.
Normalize at the single point that consumes the value instead, so the
enforcement is structural. Truncation is idempotent and the write path
already truncates, so no digest changes — verified by writing a chain with
the previous commit and validating those same rows under this one.
The `assert_ne!` test that pinned the trap moved down a level: it now asserts
on the RFC-3339 preimage (`.123456789` vs `.123456`), which is the property
that actually causes the split, and a new test asserts `compute_hash` yields
the same digest either way.
Signed-off-by: Shani Singh <[email protected]>
0 commit comments