api.py: remove 50KB truncation from /api/corpus/retry (completes F14)
The F14 fix on 2026-05-01 removed text[:50000] truncation from watcher.py, ingest.py, and corpus_integrity.py. The retry endpoint in api.py was missed — clicking 'Retry' on an ingest-failed file in the SettingsPanel re-introduced the exact truncation pattern F14 was meant to eliminate. Found by Track 1 inventory 2026-05-02 (Finding 2 / divergence #2).
This commit is contained in:
+1
-1
@@ -1071,7 +1071,7 @@ async def corpus_retry(request: Request, auth: str = Depends(require_auth)):
|
|||||||
ON CONFLICT (source) DO UPDATE SET
|
ON CONFLICT (source) DO UPDATE SET
|
||||||
full_text = EXCLUDED.full_text, char_length = EXCLUDED.char_length,
|
full_text = EXCLUDED.full_text, char_length = EXCLUDED.char_length,
|
||||||
enqueued_at = NOW(), completed_at = NULL, failed_at = NULL, attempts = 0
|
enqueued_at = NOW(), completed_at = NULL, failed_at = NULL, attempts = 0
|
||||||
""", (source, text[:50000], len(text)))
|
""", (source, text, len(text)))
|
||||||
cur.execute("""
|
cur.execute("""
|
||||||
UPDATE ingest_failures SET retry_count = retry_count + 1, last_failed_at = NOW()
|
UPDATE ingest_failures SET retry_count = retry_count + 1, last_failed_at = NOW()
|
||||||
WHERE source = %s
|
WHERE source = %s
|
||||||
|
|||||||
Reference in New Issue
Block a user