Trim heavy search stages to avoid 504
build-push / docker (push) Successful in 4m2s

This commit is contained in:
AI Assistant
2026-03-16 13:55:10 +09:00
parent c92ef97c98
commit a37e02aea9
4 changed files with 18 additions and 7 deletions
+11
View File
@@ -341,6 +341,17 @@
- [ ] full browser-level validation was not fully reproducible in this environment
## Recent Change Log
- Date: `2026-03-16`
- What changed:
- Reduced the heaviest search-stage caps slightly: fewer query variants per request, smaller per-source result caps, lower enrichment scope, and a bounded Gemini candidate set.
- Why it changed:
- The widened search configuration was pushing the request past the reverse-proxy timeout and surfacing `504 Gateway Time-out`.
- How it was verified:
- `go test ./...`
- `bash scripts/selftest.sh`
- What is still risky or incomplete:
- Search coverage is still broader than the original baseline, but there is now an explicit tradeoff between result volume and request latency.
- Date: `2026-03-16`
- What changed:
- Increased collector result caps and widened source-specific search query templates for Envato, Artgrid, and Google Video.