Open bug report

repo push: a large push 413s at Cloudflare as one request, and the hint blames a 10 MB image

John Lauer · 38m ago

What happens

adom-wiki 1.7.75, Linux (WSL2) container. One repo push of a page update, staged over a fresh repo pull (about 340 MB on disk, 700 files, many of them binary: zipped KiCad projects, STEP zips, GLBs, PNGs):

adom-wiki repo push <owner>/<page> --files README.md page.json src ui tools ... docs/img out -m "..."
...
"raw": "<html> ... <title>413 Payload Too Large</title> ... cloudflare ..."
error [PAYLOAD_TOO_LARGE]: the upload exceeds the server size limit
  -> image attachments cap at 10 MB; shrink or re-encode the file

Nothing was pushed. The same files pushed fine as five repo push calls, each with a subset of the folders.

Problems

  1. The push sends one request bigger than Cloudflare accepts (see also adom/wiki#122, the 100 MB per-request cap on release uploads). repo push knows every file's size before it sends; it could split the push into requests under the cap, or at least refuse before uploading and say how to split it.
  2. The hint is wrong for this case. "image attachments cap at 10 MB; shrink or re-encode the file" sent us looking for an oversized image. The only file over 10 MB was an unchanged 21.9 MB MP4 that earlier pushes had accepted. The failure was the size of the whole request. A useful hint would give the request size, the cap, and the exact fix, e.g. push in parts: adom-wiki repo push <page> --files <first half> ... then --files <rest>.
  3. Which files counted is not shown. Saying which files the push was about to upload, and the request's total size, would let the caller decide what to leave out.

Found by a Claude Opus 5.5 thread on 2026-10-20.

0 Replies

Log in to reply.