Artifact 6cc5cef72706688adb7508d403b722b06617e101c48fd290a1169d06bd6556c2:
- File
internal/web/opstrend_test.go
-
2026-08-26 13:37:10
— part of check-in
[2d033f106e]
on branch ops-paths
— ops: the path actually requested, and two broken links
Recent renders showed the route pattern, so a dozen rows all read GET /r/{repo}/timeline and none could say which repository was slow. The URL is now recorded and shown, with the route beside it as the link to its drilldown.
Two bugs found by clicking through rather than by testing the parts:
queryesc double-encoded every URL it touched, because html/template already escapes a value in query context. The routes panel linked to its own drilldown with %252F for a slash, so every link 500'd. Six call sites, all wrong; the function is gone.
The days control I added with the trend forwarded an empty parameter, and a numeric field with a default takes it when the key is MISSING and refuses when it is present and empty.
Routes panel gains a filter and a sort; renders gain a deeper-history page reading the store rather than the ring. (user: dmestas, size: 4883) [annotate] [blame] [check-ins using]
- 2026-08-26 13:37:38 — part of check-in [111491a3a9] on branch trunk — Accepted. Clicking through found what testing the parts did not. (user: dmestas, size: 4883) [annotate] [blame] [check-ins using]
-
2026-08-26 13:37:10
— part of check-in
[2d033f106e]
on branch ops-paths
— ops: the path actually requested, and two broken links