fix: accept 24 MP camera photographs

[TorstenDittmann]

Problem

A production 6000×4000 PNG (~28 MiB, 24 megapixels) could not be analyzed. The request was rejected before inference:

1. 10 MiB upload cap — the PNG is 26.7 MiB, so /analyze returned 413.
2. 20 megapixel decode ceiling — 6000×4000 is 24 MP, so decode would also 413 even if the body were smaller.

The image itself decodes cleanly; the limits were the only failure.

Change

• Raise the request limit from 10 MiB to 32 MiB (covers this photograph with headroom).
• Restore the decode ceiling from 20 MP to 40 MP, which was the original value and still rejects decompression bombs.
• Lock the production dimensions (6000×4000, 28,026,017 bytes) into unit tests, and document the new limits in the README and docs site.

The original photograph is not redistributed.

  

[appwrite]

Autogravity

Project ID: 6a9e5d640016fa6fb653

Sites (1)

Site	Status	Logs	Preview	QR
Docs autogravity-docs	Ready	View Logs	Preview URL

Tip

SSR frameworks are fully supported with configurable build runtimes

[greptile-apps]

Confidence Score: 4/5

The runtime limit changes appear sound, but the explicit repository testing requirement must be satisfied before merging by replacing the implementation-coupled checks with a valid end-to-end behavioral regression.

Findings

1.  Implementation-Coupled Regression Tests ▶

Fix with agent prompt

### Issue 1
cmd/autogravity/main_test.go:324-337
`TestProductionPhotographFitsLimits` only compares duplicated dimensions and byte counts with `maxRequestBytes` and `imageutil.MaxPixels`. The related header-only test also requires decoding to fail, and the existing valid fixtures are all small. As a result, these tests can remain green even if a valid 6000×4000 image cannot be decoded or accepted by the handler. This violates the repository directive to test observable behavior rather than mirror source configuration. Replace these checks with a valid generated or fixture image that exercises successful decoding or handler acceptance; this repository requirement must be satisfied before merging.

---

For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.

Summary

• The runtime and documented limits are aligned.
• Request and decode admission remain concurrency-bounded.
• The new production-photograph tests mirror implementation limits rather than proving successful behavior with a valid image.

_{Reviews (1) · Last reviewed commit: "fix: accept 24 MP camera photographs in ..."}

[greptile-apps]

Implementation-Coupled Regression Tests

TestProductionPhotographFitsLimits only compares duplicated dimensions and byte counts with maxRequestBytes and imageutil.MaxPixels. The related header-only test also requires decoding to fail, and the existing valid fixtures are all small. As a result, these tests can remain green even if a valid 6000×4000 image cannot be decoded or accepted by the handler. This violates the repository directive to test observable behavior rather than mirror source configuration. Replace these checks with a valid generated or fixture image that exercises successful decoding or handler acceptance; this repository requirement must be satisfied before merging.

Context Used: Call out and harshly judge implementation-coupled tests. We don't mirror source code, configuration, or version pins in assertions. We test observable behavior; use linters for syntax and schema checks. (source)

Knowledge Base Used: CLI integration and evaluation

Prompt To Fix With AI

This is a comment left during a code review.
Path: cmd/autogravity/main_test.go
Line: 324-337

Comment:
**Implementation-Coupled Regression Tests**

`TestProductionPhotographFitsLimits` only compares duplicated dimensions and byte counts with `maxRequestBytes` and `imageutil.MaxPixels`. The related header-only test also requires decoding to fail, and the existing valid fixtures are all small. As a result, these tests can remain green even if a valid 6000×4000 image cannot be decoded or accepted by the handler. This violates the repository directive to test observable behavior rather than mirror source configuration. Replace these checks with a valid generated or fixture image that exercises successful decoding or handler acceptance; this repository requirement must be satisfied before merging.

**Context Used:** Call out and harshly judge implementation-coupled tests. We don't mirror source code, configuration, or version pins in assertions. We test observable behavior; use linters for syntax and schema checks. ([source](https://app.greptile.com/review/custom-context?memory=instruction-0))

**Knowledge Base Used:** [CLI integration and evaluation](https://app.greptile.com/appwrite/-/custom-context/knowledge-base/appwrite/autogravity/-/docs/cli-validation.md)

---

For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.