Skip to content
zit Check-in [09d191e634]
Login

Check-in [09d191e634]

Overview
Comment:Release 0.3.18

The file-history index is built by the derive at ingest, fossil's way.

Timelines: family | ancestors | descendants | both | trunk | version-0.3.18
Files: files | file ages | folders
SHA3-256: 09d191e634626f83026a00b53a21915e24f5080137d3d97466789aad0ddf887f
User & Date: dmestas on 2026-09-16 22:11:26.598
Other Links: manifest | tags
Context
2026-09-16
22:58
ci: do not run the battery a second time on a tag push

A release tag lands on a commit whose branch push already ran ci, and the tag push ran it again on the same three single-slot runners the release workflow was queueing for. Every branch push still runs; the release workflow, triggered by the tag, gates what it ships. check-in: e9e2ba4431 user: dmestas tags: trunk

22:11
Release 0.3.18

The file-history index is built by the derive at ingest, fossil's way. check-in: 09d191e634 user: dmestas tags: trunk, version-0.3.18

22:11
file index: built by the derive, at ingest

fossil fills mlink as each check-in arrives and answers finfo by lookup. zit's derive computed the same row per check-in and dropped it; the index was rebuilt by a separate pass on the first PATH query, 6.8 min on pkgsrc and not resumable. The derive now hands each change set to an index builder as it links, stores it beside the checkpoint, and extends it over the tail on append; a cache hit computes nothing. The on-query build is the fallback and checkpoints every 8192 entries. Index format 4 records completeness so a partial checkpoint is never adopted whole. crosslink reports a tree's files instead of unknown. pkgsrc, fresh clone to first answer: 11.7 min -> 7.1 min + 1s. check-in: df99743ca4 user: dmestas tags: trunk

Changes