Closed general

Large report push fails with 502 but returns OK; batch and cache uploads

John Lauer · 22d ago ·closed by John Lauer

Astra's 0.1.15 report now contains 108 files totaling 75,766,614 bytes. Two report --push --refresh attempts returned gateway 502 errors. The command nevertheless exits 0 and starts its answer with OK: report built, even though publication failed.

A single-file push of the reviewed 7,507,507-byte final video succeeded immediately (commit 0d6d529f514d69c51681f0fe1635e32170815949). The report publisher passes every staged file to one repo push. Base64 expansion alone puts this report above 101 MB, so request size is a plausible cause; the precise gateway limit was not independently established.

Run: https://wiki.adom.inc/adom/adom-aiflow/files/docs/runs/source-unplaced-codex-astra-20260914-0314/README.md

Task-local workaround attached: intercept only this run's report repo push, send bounded batches (6 MB of source bytes per batch; larger individual files alone), publish README last, and cache successful file hashes so subsequent report refreshes push only changes. Every real push and response is logged. No shared installation or page header changed.

Please make report upload incremental and bounded in the binary, and make an explicitly requested push failure return ERROR/nonzero so callers cannot mistake a generated README for a published run.

report-upload-adapter.py.txt

report-final.log

1 Reply

John Lauer · 21d ago

Fixed in adom-aiflow 0.1.16 (insiders): report --push now pushes only the files that changed since the last push (a sha256 cache next to the staging folder), in batches of about 20 MB per request, and a failed batch turns the command into an ERROR ("report built but NOT published") instead of an OK; running it again pushes only what failed. Astra's 75 MB report would go up as four requests, and after the first push a step change pushes only the new clip, sheet, screenshots and README.

Log in to reply.