Skip to content
zit Check-in [5da8555024]
Login

Check-in [5da8555024]

Overview
Comment:Sync and pull open the store before reading leaves for the fork report, so a torn last frame left by a crash is repaired first; the simulator counts a forked sync or pull as success
Timelines: family | ancestors | descendants | both | trunk
Files: files | file ages | folders
SHA3-256: 5da85550247dcddce85a05536815b9c68d42e623aca16155bbfaaadf4cf55f58
User & Date: dmestas on 2026-11-07 02:39:31.851
Other Links: manifest | tags
Context
2026-11-07
03:02
Release 0.11.0 check-in: b182f0e6c1 user: dmestas tags: trunk, version-0.11.0
02:39
Sync and pull open the store before reading leaves for the fork report, so a torn last frame left by a crash is repaired first; the simulator counts a forked sync or pull as success check-in: 5da8555024 user: dmestas tags: trunk
01:41
A no-op sync or pull does work in proportion to what changed: nothing is persisted when nothing arrived, the store is opened once for its settings, resolved clusters and outstanding sub-manifest references are kept in sidecars checked against the log, and fork leaves come from the cached view, so a no-op sync at 42k files costs about 7 ms of CPU instead of 476 check-in: 645e0a6060 user: dmestas tags: trunk
Changes