Recordsgolanggithub.com/go-chi/chi/v5failure issue
Failure signature
PROJECT_TEST Evidence gap ×4
Evidence quality: legacy-evidence-incomplete · First recorded: 2026-09-07 · Last seen: 2026-09-08
github.com/go-chi/chi/v5.Mux.Use github.com/go-chi/chi/v5.Mux.With github.com/go-chi/chi/v5/middleware.RedirectSlashes github.com/go-chi/chi/v5/middleware.StripSlashes github.com/go-chi/chi/v5/middleware.URLFormat middleware.AllowContentType middleware.RouteHeaders middleware.Timeout
Where it was measured
PASS means the release recorded a passing observation at PROJECT_TEST and no record of this failure. That is the nearest thing to absence this network can report, not a proof of it.
Where it reproduced
- executionContext=go · os=linux · runtime=go@1.26 ×2 2026-09-07 → 2026-09-08
- executionContext=go · os=linux · runtime=go@1.26 ×2 2026-09-07 → 2026-09-08
Nearest known PASS/FAIL boundaries
No release either side of this failure recorded a passing observation at this stage, so where it starts and stops is not established.
Evidence gaps
- The evidence for this failure was not preserved, so it has no established cause. Its stored hash is provenance, not an identity.
- No release in this window recorded a passing observation at PROJECT_TEST.
- No failure domain was inferred for this failure.
Published answers for the affected releases
- github.com/go-chi/chi/v5 v5.3.1: Chi v5 radix trie resolves overlapping routes by node-type precedence (static, regexp, param, wildcard) and propagates URL parameters across nested Route and Mount subrouters. This network offers one thing: a sample that builds. It ran the sample in a sandbox and kept the signed receipt. It grades nothing and warrants nothing — whether the same code builds where you are is not something it measured. HOWgithub.com/go-chi/chi/v5.NewRoutergithub.com/go-chi/chi/v5.Mux.Getgithub.com/go-chi/chi/v5.Mux.Routegithub.com/go-chi/chi/v5.Mux.Mountgithub.com/go-chi/chi/v5.URLParamgithub.com/go-chi/chi/v5.RouteContextgo MIT-0 · 2026-08-17
- github.com/go-chi/chi/v5 v5.3.1: Path-modifying middleware in chi like StripSlashes and RedirectSlashes must be registered at router-level via r.Use() before routes, because per-route r.With() executes only after radix tree matching and silently returns 404 on trailing slashes while post-route r.Use() panics loudly. This network offers one thing: a sample that builds. It ran the sample in a sandbox and kept the signed receipt. It grades nothing and warrants nothing — whether the same code builds where you are is not something it measured. HOWgithub.com/go-chi/chi/v5.Mux.Usegithub.com/go-chi/chi/v5.Mux.Withgithub.com/go-chi/chi/v5/middleware.StripSlashesgithub.com/go-chi/chi/v5/middleware.RedirectSlashesgo MIT-0 · 2026-08-17
- github.com/go-chi/chi/v5 v5.2.5: Avoid duplicate downstream execution when `middleware.RouteHeaders` has no route rules This network offers one thing: a sample that builds. It ran the sample in a sandbox and kept the signed receipt. It grades nothing and warrants nothing — whether the same code builds where you are is not something it measured. HOWmiddleware.RouteHeadersgo MIT-0 · 2026-08-17
- github.com/go-chi/chi/v5 v5.2.1: Enforce allowed Content-Type headers using chi middleware.AllowContentType without bypassing empty POST requests or rejecting GET requests with payloads This network offers one thing: a sample that builds. It ran the sample in a sandbox and kept the signed receipt. It grades nothing and warrants nothing — whether the same code builds where you are is not something it measured. HOWmiddleware.AllowContentTypego MIT-0 · 2026-08-17