Repository navigation
feat(core): split the updateBuild request to avoid PayloadTooLargeError - #327
Merged
gregberge merged 2 commits intoJun 29, 2026
Conversation
A single (non-parallel) build sent all of its screenshot metadata in one `updateBuild` request, which could exceed the API request body size limit (PayloadTooLargeError) once a suite grew large, since per-screenshot metadata can be sizeable. Split a non-parallel build's screenshots across several sequential `updateBuild` requests sized to stay under the limit. The build is finalized by the last request (`final: true`), which also carries the build metadata. Parallel shards keep sending a single request each, since every request counts as one batch. Regenerate the api-client types to expose the new `final` field. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Extend request splitting to parallel builds. An indexed shard groups its chunks into a single shard (only the last request is `final`); an index-less shard (manual finalization) can't be grouped, so each chunk is sent as its own complete shard, which is fine since the build is finalized manually. Build metadata is sent on the last chunk only either way. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
gregberge
deleted the
greg/arg-430-split-the-upload-request-to-avoid-payloadtoolargeerror
branch
June 29, 2026 06:59
This branch was successfully deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why
A build sent all of its screenshot metadata in one
updateBuildrequest. Once a suite grows large, that body can exceed the API's request body size limit and fail withPayloadTooLargeError, since per-screenshot metadata (test info, annotations, tags, URLs…) can be sizeable. (See ARG-430.)What
Split a build's screenshots across several sequential
updateBuildrequests, each byte-budgeted to stay under the limit (chunkBySize, < 2MB):final: trueand carries the build metadata.parallelIndex), only the last isfinal.Build metadata is sent on the last chunk only in every case.
api-client'sschema.tsis regenerated to expose the newfinalfield.Requires the matching backend change (argos
greg/arg-430-...), which must ship first.Tests
chunkBySizeunit tests (size splitting, oversized item, empty) and an integration test asserting the update request is markedfinaland carries the metadata. Types + lint clean.🤖 Generated with Claude Code