Tolerate Gemini image expansion drift
build-push / docker (push) Successful in 4m23s

This commit is contained in:
GHStaK
2026-03-24 16:29:36 +09:00
parent 1fb9919ec3
commit 3c6df2e777
6 changed files with 68 additions and 49 deletions
+14
View File
@@ -268,6 +268,20 @@
- backend debug broadcasts
## Recent Change Log
- Date: `2026-03-24`
- What changed:
- Relaxed Gemini image-query expansion parsing so loose plain-text numbered lists can still be accepted when the model prepends explanatory text instead of returning a clean JSON object.
- Removed the GIPHY image-mode search meta box from the frontend so the image UI stays visually simpler.
- Stopped surfacing the Gemini image-expansion fallback warning directly in the image-search UI when the backend can still continue with usable fallback queries.
- Why it changed:
- Real log review showed Gemini image expansion sometimes returned text like `Here is the JSON requested`, which triggered fallback even though the model output still contained useful query candidates, and the extra meta box was not adding enough value to justify the space it consumed.
- How it was verified:
- log review of `ai-media-hub-2026-03-24T07-25-42-827Z.log`
- `node --check frontend/app.js`
- What is still risky or incomplete:
- This improves tolerance for one common Gemini formatting deviation, but fully free-form model output can still fall back if it does not contain recoverable query lines.
- Go tests still could not be rerun in this environment because `go` is currently unavailable here.
- Date: `2026-03-24`
- What changed:
- Removed the redundant `GIPHY Download Dir` variable field from the Unraid template and kept the dedicated `GIPHY Downloads` path mapping as the single user-facing download-path control.