Timeline

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

A contributor is a name an author's client wrote on an artifact; an account is a login on this forge. On a mirror the two barely intersect — fossil has 151 contributors and this forge has two accounts, sharing none — so the page says so, and badges the few that are both.

Read-only on purpose. A grant control here would offer to give write access to a string, and on a mirror those strings are chosen by whoever can commit upstream. The door goes to settings, where every row is a real account.

account.list is forge-wide and site-admin only, so a repo admin gets the door without the badges rather than an error. closed check-in: 8fb0a669aa user: dmestas tags: people-admin

"151 contributors" in fossil's About panel went to the fleet page: 481 names across 25 repositories, repo nav gone, search rescoped to the whole forge. people.list has taken a repo parameter all along and nothing in the UI reached it.

The per-person line differs from the fleet's on purpose. Counting repositories inside one repository always says 1, so the span of somebody's work here is the fact worth carrying instead.

Contributors(0) meant a hundred, silently, which is why the listing said "of 100" under an About panel saying 151. It means all of them now. closed check-in: 278e021086 user: dmestas tags: repo-people

zit#136 shipped --mimetype, so a remark written in the composer is stored as the Markdown it previewed as. zit#138: the title card holds the whole -m message, so the heading takes its first line. check-in: 73367a3820 user: dmestas tags: trunk

Every other row in the About panel is icon + label, and .about-sub indents 1.5rem to clear that icon. These two had no icon, so their excerpt and date hung indented under nothing. A wrapping title also needs baseline alignment, or its later lines slide back under the icon.

The note now says who wrote it, as the feed does. check-in: d6a6146502 user: dmestas tags: trunk

Notes sat third in the sidebar, under Tags. What a project has been doing is a better first answer to "what is this" than which versions it has cut — and with no tab, this is a main door to them, which reads poorly third. closed check-in: d1dde173e0 user: dmestas tags: notes-first

zit#134: landing show has to walk the whole store to FIND the record before it can answer about it, and quarry already folded that record out of its own index. zit merge --probe names the two check-ins, so the walk disappears -- 0.005s against 0.18s on this forge's own store, and the gap widens with store size, not with the number of landings.

Probing the same tips the cache is keyed on also closes a race: the key was built from resolved tips while the probe re-resolved a branch name, so a push landing between the two cached an answer under a key it did not describe.

An unresolvable tip now skips the probe instead of keying on ':' -- every landing whose branch could not be resolved shared that one cache entry and could be served another landing's verdict. check-in: bb05986ad8 user: dmestas tags: trunk

Without a tab, /timeline?y=e is where somebody browsing notes stands, and it offered no way to the page that reads them as a feed. The other two doors — the About panel and the docs page — are not where a reader who just filtered a timeline is looking. check-in: 16e8738cb6 user: dmestas tags: trunk

A landing is a forum thread — that is what a stock fossil clone reads — but it is a decision record with its own surface. Off the listing and out of the count, which must agree. An existing thread URL redirects to the record rather than 404ing a link that used to work. check-in: 302ca7fae6 user: dmestas tags: trunk

Fossil registers one timeline event per technote; quarry registered one per artifact. libfossil has 50 technote artifacts under 26 event ids, so its timeline showed a superseded title five rows above its own correction. The collapse is in the event trigger — insert, then evict every loser for the event id — which is order-independent, as the fold requires: a clone delivers artifacts in wire order.

Notes are no longer a tab. Fossil's built-in menu has none, and libfossil, which uses them as a milestone feed, overrode mainmenu to add TODOs and FIXMEs without adding one. They are reached from the About panel, the docs page and the timeline filter instead, and the listing is a feed with excerpts rather than a list of links.

Every edit stays readable, as a wiki page's revisions are.

Fixes an authoring bug found on the way: zitcli never passed --time, so an edit re-filed the note at the moment it was edited and it moved in the timeline. The filing time is now a field on both forms. closed check-in: ac80214995 user: dmestas tags: notes

Two names whose hues land 7 degrees apart painted one block. Near collisions are a birthday bound, not bad luck, so the bar resolves what is in the thread — stepping a colliding voice to the identicon's other lightness. The hue never moves: it is the identity. check-in: e1e9619d0d user: dmestas tags: trunk

An HTML response carried no cache directive and no validator, which does not mean do not cache — it lets the browser choose a freshness lifetime. Safari chose one, and served a timeline rendered before a deploy while the server answered with another; the reader sees stale state with no way to tell.

no-cache rather than no-store: the copy is still kept and reused after revalidation, so the back button stays instant. Only reuse without asking is wrong, and every one of these pages is a view of moving state. check-in: ece3b20f3d user: dmestas tags: trunk

An anchor inside an anchor is invalid — the parser closes the outer one at the inner, which tore every docs row in half. The docs list and the wiki home card are whole-card links, so their bylines go back to plain mark-and-name; the row already goes somewhere.

a.who is inline rather than inline-flex for the same family of reason: a flex box is atomic and cannot flow with the text around it. check-in: 01e7bce146 user: dmestas tags: trunk

A URL with credentials (http://user:pw@host/) leaves them on document.baseURI even though location is cleaned, and fetch() refuses any URL carrying credentials — so every enhancement failed at once: diff toggle, unread poll, diff sentinel. A server-stated <base> fixes all of them without script, since the server knows the URL from its own routing and never from userinfo.

The toggle also swallowed its own fallback: replaceState to a credential-free URL throws on such a page, and it ran before @get while __prevent had already cancelled the link — neither swap nor navigation. Cosmetics now cannot fail the click. check-in: c35d8c4b5b user: dmestas tags: trunk

Fossil routes every surface through one helper (hyperlink_to_user); quarry had thirty-two places rendering a name and none of them clickable. One 'who' helper now, applied to the twenty that name an author — the account button and participant stacks stay decorative.

timeline.list gains user=, paired with y=all: what someone did includes their wiki edits and ticket changes, not just check-ins. check-in: a18be6d78d user: dmestas tags: trunk

The ring is stroked 2.2, so it paints to r+1.1; a 4.8 disc beside it read a fifth smaller. Internals are the ring's outer edge, filled. check-in: e1f3ed4bac user: dmestas tags: trunk

Mark then name, in the page's colour, orange on hover. The sigil is syntax and the mark already says this is a person; a name that is orange everywhere stops meaning clickable anywhere. check-in: dda6810776 user: dmestas tags: trunk

An @mention now renders the same glyph as the person's byline, through the resolver seam so markup still knows nothing about accounts. The identicon moved to internal/idn — web and api each hashed the name separately and agreed by luck. Blockquotes had no rule at all. check-in: 0ba22dea9e user: dmestas tags: trunk

f-post-h and f-post-b are where the padding lives; naming the wrapper alone gets a border round unpadded text. Check-ins use the same bordered list every other listing in the forge uses. check-in: 20373a1806 user: dmestas tags: trunk

The composer's textarea has no border of its own — it is built for the f-reply wrapper the ticket page and forum use, and without it the tabs and text floated unframed. The diff is a details now: this page is where a decision is made, and 600 lines between the proposal and the buttons means scrolling past the change to reach them. check-in: 59d7d8fa4c user: dmestas tags: trunk

Textually clean, but branchTipOf called Timeline with the old positional signature — ported to TimelineFilter. check-in: dae2180a89 user: dmestas tags: trunk

Fossil lets an author correct a check-in comment after the fact; quarry showed the superseded C card as if it were current, on 697 fossil check-ins. The correction is now applied at read, batched in AttachCI, with the original kept beside it — the stored card is an artifact fact and stays untouched. hidden and closed surface too.

Branch diff is the branch against its fork point, which is not the landing page's base (the target's current tip). Offered only where a fork point exists.

The manifest view renders the eight cards that are not the file list and counts the other 980, linking the tree.

Also: unified/side-by-side now swaps in place via datastar, keeping the window and correcting the URL; the wiki note panel lets blocks use the full width while prose keeps its measure. check-in: ff7f5d3d69 user: dmestas tags: trunk

docs/landings.md covers the whole loop and says plainly that a landing is a forum thread plus branch tags. Writing it found the gap: there was no create control at all. A mirror offers its upstream instead. check-in: c6aa693938 user: dmestas tags: trunk

open, comment, reject, accept through the forge against a real store — accept merges to trunk via zit#131's bare-store path. Also checks the record still reads as an ordinary forum thread. check-in: 9a84a5d962 user: dmestas tags: trunk

The probe is a full-store scan by design and measures 2.0s here, paid on every view. Keyed on the two check-ins, so a push invalidates it by making a different key rather than by anyone clearing a cache. 1.9s cold, 50ms warm. check-in: 21d510a5bd user: dmestas tags: trunk

A proposal is changes with reasons attached; a diff keeps the changes and throws the reasons away. zit#133's display half, from our own index. check-in: 120277efc7 user: dmestas tags: trunk

zit#131 landed the probe and exit 5. A conflicted landing renders as blocked with its paths named and accept disabled; a refused accept is a state to show, not a fault to report. Unknown is never treated as clean. check-in: e0f59b6abf user: dmestas tags: trunk

Stats are tallied at parse time so a windowed diff reports the whole file, and sit on the file header as well as the summary line. Tags come from checkin_tag, newest word per name winning. Copy falls back through execCommand to selection: navigator.clipboard is undefined on the plain-HTTP origins quarry is usually served from. check-in: ac056aaa1d user: dmestas tags: trunk

The timeline already had them; the ticket list did not — its row uses .Created and my earlier pass patched a different template that uses .Opened. Also added to ticket timeline entries and the forum queue.

The note is no longer folded when long. It was folded past ~1200 bytes because fossil's auto-toc note runs three screens and pushed a timeline below the fold, but a note written about this artifact is the context you came for. The summary stays, so it can still be collapsed; the threshold and the NoteLong field it fed are gone rather than left dead. closed check-in: eb1f126e04 user: dmestas tags: idn-open

Fossil's Context panel: the check-in among its neighbours in time, which is the question somebody bisecting a regression is asking. Two bounded index walks, no store read.

Needed a new index — every index on checkin led with branch, so ordering by date alone was a full scan of 20,928 rows plus a sort, twice a page. checkin_by_date puts the panel back at ~10ms.

Nodes reuse the timeline's palette so a branch is one colour across the forge. One lane deliberately: three neighbours are a slice of time, not a graph. On a phone the row stacks and the drawn rail becomes a border, since an SVG node cannot stretch without distorting its circle.

Identicons now appear wherever a person is named — check-in metadata, context rows, timeline, technotes, chat, attachments, wiki history. closed check-in: f73b5b9f05 user: dmestas tags: ci-context

A list of what awaits a decision and a page per record: proposal, diff against target computed at view time, discussion, and the controls. accept rides `i` because it merges; everything else is a forum cap. Transitions render as events — zit stores them as replies, which is encoding the interface exists to hide. check-in: 7d2a820f65 user: dmestas tags: trunk

Comment links resolved only hashes and http URLs, so fossil's own Markdown and limitations rendered as raw markup. They now go through the same route table the wiki renderer uses, and an unmapped one degrades to its label instead of showing brackets.

About moves below the comment and metadata — fossil's order. Above the title it was an empty bar floating over the page name.

checkin.diff returned the raw patch on every call and nothing read it: ~78KB of duplicate serialised and parsed back per view. Now opt-in. Diffs are also memoised per immutable pair, like listings already are. closed check-in: 7a2510835d user: dmestas tags: checkin-page

A landing (zit#127) is a reading of forum_post, not a new artifact kind, so the table is derived and recomputed whenever any post in its thread folds -- which is what makes a reply indexed before its root converge on the same row. Backfilled once at open for indexes whose posts predate the table. check-in: 3c6bee847a user: dmestas tags: trunk

A merge whose two parents are both on trunk puts two chains in front of one column. Claiming rail 0 anyway stopped drawing the line that was already travelling there — the gap — and overwrote the commit it was heading to. Test asserts every head resumes its predecessor's tail. check-in: 6f34d948a0 user: dmestas tags: trunk

The edge resolved a CapSet and threw it away; it now rides the context, so an op can ask which letters the caller holds. Private tickets list, count and resolve for e, and for nobody else. One privacyWhere() so a fourth read path cannot silently ship without the clause. check-in: 9b2b188ece user: dmestas tags: trunk

The capability exists now (RFC 0004), so private_contact and contact are withheld by default and rendered to a holder of e. Default deny with no ungated-forge exemption: that rule would publish them. check-in: 86fadebbab user: dmestas tags: trunk

One ticket changed nine times is nine rows here. "tickets 93,649" against 17,000 tickets had the right number and the wrong noun. check-in: bcdf35bcef user: dmestas tags: trunk

A chip counted its kind across the repository but paged a window of the whole timeline, so 234 tickets among thousands of check-ins gave ten pages with rows on almost none. Timeline takes a kind; event_by_kind covers it. check-in: 0238002099 user: dmestas tags: trunk

Every .idn rule was scoped to a parent — .avatar, .ft-meta, .f-post-h — so an identicon used anywhere new inherited no size, and an SVG with no size fills its container. The wiki history page rendered one person's mark at the width of the screen. A helper meant to be usable wherever a person is named has to be safe by default; the scoped rules are more specific and still win.

Also drops the centring from the doc grid. It indented the block away from the page title, which sits outside the grid: on a doc page the heading started at 392px and its first paragraph at 495px. closed check-in: 717dbf0f20 user: dmestas tags: idn-base

Sizing the grid to what each page happened to hold made the prose jump sideways every time a reader clicked from a page with headings to one without. The text should sit where it sat: the contents track is now always reserved, and an empty one costs nothing but space it was going to occupy anyway.

The left rail still follows :has — a doc page has no siblings to list, and reserving a gutter for nothing is a different mistake. closed check-in: 6d2a12980e user: dmestas tags: doc-reserve

Infinite scroll out, a real pager in: page numbers with both ends pinned, position, and every page a bookmarkable URL. The feed pages by offset now (a page is a position, not a place you arrived from) and says how far it reaches — 264K events is not a pager, it is an archive, and that lives on each repository's timeline. check-in: 98f77c8273 user: dmestas tags: trunk

fossil content links its documentation absolutely — the Cookbook has importing from Git — and the route mapping sent those to the file view. That was right when the file view was the only thing there was; since doc.get exists it has been putting readers in a source listing of a page quarry can render.

Leaves /uv/ dropped: unversioned content is a fossil feature neither quarry nor zit has, and that is why Download renders as plain text rather than as a link to a 404. closed check-in: d53f14d5b5 user: dmestas tags: doc-links-abs

Fossil's own docs link directories with a trailing slash — index.wiki carries a variety of techniques — and those all 404'd: the doc route found no renderable extension, redirected to the file view, and the file view cannot serve a directory. A real page was sitting behind the error the whole time (www/caps/index.md).

A directory now serves its index document, preferring the formats that render into the page, found with one listing rather than a probe per candidate. A directory with no index goes to the TREE view; only an actual file falls back to source. closed check-in: ff17aa2517 user: dmestas tags: doc-dirs

A fixed window is a dead end for anyone whose repositories are busy. Cursor is date~hash, so the merged stream cannot repeat or skip where two events share a timestamp. Sentinel

• loads the next page on scroll; noscript holds the same page as a link.

At 1800px the article ended 391 pixels short of the contents rail. That was not breathing room, it was a hole: the column took 1fr while the article capped at the measure, so the leftover sat between them.

The column now sizes to its content and the block centres. Running text still caps at the measure — 73 characters a line, where reading wants 45-75 — but a code block, a table or a diagram gets the whole column, because wrapping those to prose width is what makes people scroll sideways. Measured on fossil's th1.md: prose 625px, code up to 1216. closed check-in: d11bec1130 user: dmestas tags: doc-measure

Fossil's wikitheory.wiki: pages named branch/NAME or checkin/HASH are associated with that branch or check-in, and fossil shows them in an About section on those screens. Hiding them from the documentation index without this made 49 of fossil's 83 wiki pages reachable only by typing the URL — half the fix, and the worse half.

Notes now appear above their branch's timeline, their check-in, their ticket and their tag. A branch note shows only when the timeline is narrowed to that branch: above every branch it is a caption on the wrong picture.

Long ones start folded. Fossil's own auto-toc note runs three screens and put the timeline entirely below the fold, which is an About that has buried its subject. closed check-in: 9b9618a12f user: dmestas tags: assoc-notes

Resolved twice against work that landed on trunk in parallel — the wiki structure panel and saved views. All three are orthogonal; nothing was dropped. Truncation goes, since paging replaces it. check-in: ce412bd621 user: dmestas tags: trunk

A saved view is a name for a URL the tracker could already produce, so it stores the name and the query and nothing else. Per account, per listing; forgetting one loses the shortcut and not the listing. check-in: 96181d8fcb user: dmestas tags: trunk

Wiki pages alone did not need paging — human authorship bounds them at a couple of hundred — but the tree half is unbounded, and the old 400 cap was a dead end with everything past it reachable only by guessing a filter. Pages of 100, since these are one-line rows in two columns.

One function builds every link, so a filter, a sort, a page and the associated-wiki choice cannot lose each other; a stale offset lands on the first page rather than an empty one. The pager type is shared with the tracker now, which is what it always was. closed check-in: fa70fc4958 user: dmestas tags: docs-paging

Orphans and wanted pages, derived from the live text so they cost no storage. Fossil's [Name] is prose until it resolves, so only [[Name]] asks for a page. Filter and sort stay hidden until the list is long enough to need them. check-in: 09d6dfb0ad user: dmestas tags: trunk

Associated wiki — branch/, checkin/, tag/, ticket/ — are notes attached to another artifact, shown on that artifact's page; fossil's own index hides them behind a Show associated wikis checkbox. They are 49 of fossil's 83 wiki pages, so listing them made the index 59% notes about something else. Now hidden, with the same opt-in fossil offers.

Replaces the namespace-collapsing from the previous check-in: that treated the symptom, this is the rule fossil actually defines.

The front door is pinned — a documentation directory's own index, else the README — since fossil has no per-document importance metadata and convention is the honest substitute. Tree documents now carry the author of their last change, which the batched date query was already reading and throwing away. closed check-in: 8459b994d1 user: dmestas tags: docs-tab

Leads with the tickets somebody else answered and left with you, which needs no stored last-seen. Two columns, not three: the third was the feed filtered to one author. The feed's kind chips count exactly the rows they show. check-in: 837a5c908a user: dmestas tags: trunk

The wiki tab showed half a project's documentation. On fossil's own repository it lists 83 pages — 35 branch/ working notes, 7 test fixtures, and 41 real pages last touched in 2018 — while the 113 current documents under www/ had no way in at all.

The tab is now docs and lists both stores in one shape, sortable by name or recency, filterable across both. Where a page is STORED decides how it is edited, not what it is, so the source is a quiet marker on the row rather than a separate section. Namespaces of three or more pages collapse to one row that filters to itself, which is how 35 branch notes stop burying the rest. /wiki keeps working as a permanent redirect.

No count on the tab: the tree half costs a subprocess to size, and a badge reading 83 above a list of 211 is worse than no badge. check-in: 7e2839cf4c user: dmestas tags: docs-tab

/tickets is the same report machinery pointed at all granted trackers: repository becomes a browse axis, rows carry their own repo, and the board and New button stay behind since neither has one repo to mean. check-in: 94a2276f2c user: dmestas tags: trunk

Fossil's docs link each other as Quick Start and those stayed literal text, so a rendered doc was a dead end. Relative targets now resolve for tree documents only — a wiki artifact sits at no path and must not emit links relative to one — and the href is left relative so the browser resolves it against the doc's own URL. Images are served as bytes under the same route the markup already points at.

Also stops double-escaping a character reference the author wrote: fossil's own index rendered "Tips &amp; Hints". closed check-in: 44ba7c78f8 user: dmestas tags: doc-links

The dashboard borrowed ul.tickets; when the tracker became a card it grew three boxes. Its lists are dash-list now, and a feed row shows the commit subject instead of the whole message. check-in: 86bb035b9a user: dmestas tags: trunk

A repository's own docs live in its tree — fossil keeps all of www/ there, not as wiki artifacts — so until now they could only be read as source. /doc/<version>/<path> renders .wiki, .md, .html, .txt and .pikchr, mirroring fossil's dispatch, and anything else redirects to the source view rather than erroring. The URL mirrors the tree path, so a relative link between documents resolves by ordinary browser rules.

Embedded HTML goes through the sanitizer rather than out as written: fossil serves it near as-is and warns about CSP, but quarry serves other people's repositories.

Closes the shape of #6ff10002. closed check-in: af13ea62ef user: dmestas tags: doc-render

/file/trunk/... printed "trunk" as a check-in link, which 404s. The ref now goes to zit for resolution — never the index's branch table, which answers with a branch literally named trunk and is a stale lie on any repository that renamed its default (tk). Only a symbolic ref pays for the lookup. closed check-in: d62d6dfbfb user: dmestas tags: file-version

Node measured in the rail's own weight — line, ring gap and centre dot all 2.5 — so it reads as the logo instead of a squashed version. The upward line on tips was mine: hadAbove read a rail alloc had just pointed at this commit, so every tip drew a line to nothing. check-in: f312b5951d user: dmestas tags: trunk

go:embed reads from disk, so the build was green locally while the file was untracked — a fresh checkout would have failed to compile. closed check-in: 5d5aa3902e user: dmestas tags: wiki-read

Long pages were unreadable: fossil's Cookbook runs 26,000 pixels with 51 headings, no contents, and lines of ~152 characters — its author had hand-written an index at the top, which is the need stated in the only place they could state it. Headings now carry anchors whichever format wrote them (Fossil wiki passes raw HTML through, so half a fossil corpus had none), a contents rail tracks the reading position, and the measure is capped near 65.

The index gains a filter, a sort, revision counts, two columns and the Home page pinned above them. Not paged: the largest wiki in this corpus is 172 pages, and a browse list you page through is one you cannot scan.

Also fixes the global nav-link box leaking into both new rails and into the ticket rail, which drew a border around the current entry. check-in: c195eed2fb user: dmestas tags: wiki-read

The hue was a raw hash mod 360, so two names could land a few degrees apart — ticket-list and fossil-caps rendered as one magenta. Hues now come from nine slots at least 30 degrees apart, with the mainline's blue and the accent's orange left out; a branch keeps its hashed slot unless another branch in view wants it, and assignment is by name so it never depends on commit order. check-in: a754d20b3c user: dmestas tags: trunk

Authenticate accepts an imported §6.3 credential once and upgrades the account to argon2, dropping the imported secret; a wrong guess never consumes it. quarry users pull without --url now reads the store's own table (zit#124/#125) — no credential needed for a repo we already serve. Proven end to end against a real fossil: a user who existed only there signed into quarry with their original password. check-in: 41b085ae25 user: dmestas tags: trunk

The table computed a next page and never rendered it, so a tracker over 50 tickets simply ended. Both views now page by offset with a position line and both ends drawn. Triage order is computed in Go over the fetched rows, so it stays a bounded single page rather than pretending to page.

Only PageURL sets an offset: every other control returns to page one. closed check-in: 0507def643 user: dmestas tags: ticket-paging

State axis with real counts, GitHub-shaped rows, report filters in six axes, a query box that parses into them, table and board views, a browse rail, and a .json link on every report. Chips now mute the value nearly every listed row shares. check-in: a8c4a6c7f5 user: dmestas tags: trunk