Artifact b58de1203c6d69060513264c589788bcad06ba128a1522eca3556637a4a4787c:
- File
internal/web/chrome_test.go
-
2026-08-24 21:19:47
— part of check-in
[8df971b482]
on branch tree-search
— search: the tree is searchable — documentation and source
quarry rendered both as first-class surfaces (the docs tab, the file browser) and could find neither. Fossil searches documentation but not source; this does both, from one pass.
One tarball, not a read per file. cat per path costs a subprocess and a store open each: 2,199 files on sqlite is ~31s, against 2.2s for one archive — the tarball is the whole tree in one pass, which is the shape of the question.
Tip-only. Indexing every revision of every file would dwarf the rest of the index many times over to answer a question nobody asks; what a file used to say is a question its own history answers.
ref carries the version, not just the path: a link has to name the check-in the row was indexed at, and resolving a branch name at click time would be a second source of truth about which tree the row describes.
Binaries and files over 1MB are skipped and counted — a search that silently covers less than the tree beside it is the failure this change is about. (user: dmestas, size: 39922) [annotate] [blame] [check-ins using]
- 2026-08-24 21:19:54 — part of check-in [cd06e1345b] on branch trunk — merge tree-search into trunk (user: dmestas, size: 39922) [annotate] [blame] [check-ins using]
-
2026-08-24 21:19:47
— part of check-in
[8df971b482]
on branch tree-search
— search: the tree is searchable — documentation and source