Artifact d524549e68375579646fa0ffa12c95e6a07b6fbce3ee43b07da728cc07d0ad3c:
- File
internal/web/repopath_test.go
-
2026-08-25 21:49:04
— part of check-in
[059fe0bdde]
on branch ops-drill
— ops: record which repository a render was for
Repo was read with req.PathValue in the outermost middleware, where the router has not set it — path values live on the request the mux passes DOWN, a copy that middleware never sees. Same shape as the route-pattern bug, and it went unnoticed longer because an empty string looks like 'no repository' rather than like a failure.
Every render recorded until now carried an empty repo: 61 of 61 rows in the analytics store, on a fleet where repository size is the dominant cost of almost everything. The drilldown's by-repository table showed a single '(none)' row, which is what surfaced it.
Read from the path instead, unescaping as the router would. (user: dmestas, size: 1058) [annotate] [blame] [check-ins using]
- 2026-08-25 21:53:53 — part of check-in [7059271e59] on branch trunk — Accepted. It can now say which repo and which calls — which is the difference between finding a slow route and fixing one. (user: dmestas, size: 1058) [annotate] [blame] [check-ins using]
-
2026-08-25 21:49:04
— part of check-in
[059fe0bdde]
on branch ops-drill
— ops: record which repository a render was for