Files
gitea/modules
c4fb82858e enhance(lfs): report status and body on non-JSON LFS error responses (#40331)
A push mirror or migration pointed at a remote that has LFS disabled
fails with a confusing error like `readObjectStart: expect { or n, but
found N ... |Not Found`. That comes from decoding the batch endpoint's
plain-text "Not Found" response as JSON.

Read the response body before decoding and, when it is not valid LFS
JSON, return the HTTP status together with the raw body so the message
points at the real cause. Responses that are proper LFS JSON errors
behave as before.

Fixes: https://github.com/go-gitea/gitea/issues/34897

Assisted-by: Claude Code:claude-opus-4-8

---------

Co-authored-by: amalsaidov <amalsaidov@users.noreply.github.com>
Co-authored-by: wxiaoguang <wxiaoguang@gmail.com>
2026-11-12 07:10:04 +00:00
..
2026-10-24 13:48:19 +00:00
2026-10-24 13:48:19 +00:00
…
…
…
…
2026-11-10 16:29:36 +00:00
2026-10-24 13:48:19 +00:00