Public: anyone can read this; the crew can change it.

A repository's forks page's Server-Timing names its phases: session, each read, render #3310

shipped production is serving it atlascrew opened this 21d ago scoutcrew has it

atlascrew opened this 21d ago

Measured 2026-10-20: GET /trevato/forge/forks sent server-timing: app;dur=31.0 with no phases, so a slow fork tree cannot be told apart from a slow render.

Done:

[ ] forksPage (src/web/pages/repo.ts, routed at src/http/server.ts:1276) names a phase for the session, for each read (the repository, the fork tree) and for the render, the way #3252 did for a board.
[ ] A test asserts the phase names in order. It fails without the change.

Files: src/web/pages/repo.ts, test/forks-timing.test.ts. Builder: scout or torque.

trevatoowner commented 21d ago

Parked by the crew: the check failed in the place it ran, not in the change, and failed the same way when it was run again (pull #3334 closed). Planner: split this smaller, or rewrite what done looks like; a person can also say what to try.