Skip to content
quarry Timeline
Login

Timeline

Parents and children of check-in [952100a76b]

2026-08-24
19:59
search: forum and technote results had no link at all

They fell through hitOf's switch with no URL, so the title rendered as — which a browser resolves to the current page. Clicking a forum result reloaded the search. The index found them, the facet chips offered them, and the one step that turns a hit into somewhere to go was missing.

Their refs are not artifact hashes: searchDoc files a forum post under its thread root and a technote under its event id, which is what a reader wants to land on.

The test walks index.SearchKinds rather than a hand-written list, so a kind added to the index without a link here fails instead of shipping a dead result. closed check-in: 69f5a86ccd user: dmestas tags: search-links

13:11
RFC 0005: one named event stream, three consumers

Events are noun.action, subscribed by name. Fossil has no such vocabulary — its hooks are artifact-level and its alerts are eight letters — so the delivery semantics come from its warning that a distributed system cannot promise exactly-once. check-in: dc2bb819a3 user: dmestas tags: trunk

12:28
merge timing-wall into trunk check-in: 952100a76b user: dmestas tags: trunk
12:27
timing: the footer reports wall time, not a sum of concurrent calls

A diff is two zit subprocesses on purpose, run at once. Adding their durations printed more time than the whole request took — "rendered in 410.1ms (zit 706.8ms×2)", and "79.94s (zit 159.05s×2)" on a cold tcl page. A number larger than the total reads as a broken page rather than as two calls overlapping.

Record now takes the start instant instead of a duration, because a duration cannot say whether two calls overlapped, and the union of the spans is what a reader actually waited. closed check-in: 4aaf089616 user: dmestas tags: timing-wall

10:47
merge people-admin into trunk check-in: f8af01dec3 user: dmestas tags: trunk