docs(runbook): note the code-search 500 upstream panic (#113) #155

Sammanfogat

supernaut sammanfogade 1 incheckning från docs/113-code-search-500-known-issue in i main

2026-07-19 21:08:39 +00:00

supernaut kommenterad

2026-07-19 20:58:59 +00:00

Ägare

Triage — this is an upstream Forgejo bug, not our config

The panic is in Forgejo's explore.Code handler (explore/code.go:25, index out of range [12] with length 12) on Forgejo 16.0.0 — an off-by-one in result rendering, query-specific (q=ansible reliably; most queries, including far larger result sets like q=bitborg, are fine). Nothing in our zoekt config triggers or fixes it.

Actions taken / recommended

Documented as a known issue in the runbook zoekt bullet (this PR): repro, that it's upstream, the forgejo_repo_indexer_enabled=false escape hatch, and the (untested) bleve stopgap.
Not a rollback. Code search works for the vast majority of queries; disabling it over one upstream edge case would be a net loss.
bleve stopgap — evaluate, don't switch prod blind. The panic is in result rendering, so switching forgejo_repo_indexer_type may or may not avoid it; it also forces a full reindex. Test in a local/preview instance first.
File upstream. Recommend filing on the Forgejo tracker with the exact repro (GET /explore/code?q=ansible → 500; q=ansible%20playbook → 200) if not already reported, and tracking the fix. (Left to a maintainer with a Codeberg account — I can draft the report text if useful.)

Keeping #113 open to track the upstream fix.

## Triage — this is an upstream Forgejo bug, not our config The panic is in Forgejo's `explore.Code` handler (`explore/code.go:25`, `index out of range [12] with length 12`) on Forgejo 16.0.0 — an off-by-one in result rendering, query-specific (`q=ansible` reliably; most queries, including far larger result sets like `q=bitborg`, are fine). Nothing in our zoekt config triggers or fixes it. ## Actions taken / recommended - **Documented as a known issue** in the runbook zoekt bullet (this PR): repro, that it's upstream, the `forgejo_repo_indexer_enabled=false` escape hatch, and the (untested) `bleve` stopgap. - **Not a rollback.** Code search works for the vast majority of queries; disabling it over one upstream edge case would be a net loss. - **`bleve` stopgap — evaluate, don't switch prod blind.** The panic is in result *rendering*, so switching `forgejo_repo_indexer_type` may or may not avoid it; it also forces a full reindex. Test in a local/preview instance first. - **File upstream.** Recommend filing on the Forgejo tracker with the exact repro (`GET /explore/code?q=ansible` → 500; `q=ansible%20playbook` → 200) if not already reported, and tracking the fix. (Left to a maintainer with a Codeberg account — I can draft the report text if useful.) Keeping #113 open to track the upstream fix.

supernaut tvångsskickade docs/113-code-search-500-known-issue från 5463501756

ci / ci (pull_request) Successful in 12s

Detaljer

till 20af17bf1a

ci / ci (pull_request) Successful in 15s

Detaljer

2026-07-19 21:07:36 +00:00

Jämför

supernaut sammanfogade incheckning 99ecac04b1 till main

2026-07-19 21:08:39 +00:00

supernaut tog bort grenen docs/113-code-search-500-known-issue

2026-07-19 21:08:39 +00:00