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
getRecordAtTime's whole-record rebuild reads through an invalidate's stub #3614
The whole-record rebuild ignores an in-range invalidate.reconstructForward without partial collects only put/patch. An invalidate replaces the record with a stub (projection plus indexed fields), but the rebuild replays the writes before it. So a snapshot routed to the whole-record rebuild still shows fields the invalidation dropped. A newer invalidate routes snapshots there, and so do a crossed put and an evicted record. Example: put {a:1,b:2} at 10, invalidate (stub {a:1}) at 15, patch {a:3} at 18, invalidate at 20 → the snapshot at 18 shows b:2. Whether an invalidated stub should be the base depends on whether history should show the cached stub or the last known full value.
changed the title [-]getRecordAtTime reverses adds a newer plain set overwrote, and its whole-record rebuild reads through invalidates[/-][+]getRecordAtTime's whole-record rebuild reads through an invalidate's stub[/+]on Oct 27, 2026
Activity
[-]getRecordAtTime reverses adds a newer plain set overwrote, and its whole-record rebuild reads through invalidates[/-][+]getRecordAtTime's whole-record rebuild reads through an invalidate's stub[/+]