Prevent HTTP artifact limit overflow

This commit is contained in:
2026-11-19 15:19:39 +00:00
parent 6562d63a02
commit 3105f4d62f
3 changed files with 21 additions and 1 deletions

View File

@@ -124,6 +124,11 @@ and stream behavior; no new formatter or replay algorithm is needed.
## R6: Prevent artifact read-limit overflow (Stage 4)
**Complete.** The read cap no longer overflows at `math.MaxInt64`.
The new test failed before the fix and now verifies that a small file keeps
its full body and size at that limit. The existing size-limit tests, full
Go suite, race suite, vet, and build passed.
[The restricted HTTP artifact reader](../../internal/adapter/http/artifact_reader.go)
allows the same nonnegative `int64` limit as application configuration
and the CLI. It computes `maxBytes + 1` for `io.LimitReader` to detect