Fix E2B template chunk upload - #7
Merged
Merged
Conversation
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
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
1 participant
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.
The combined Runtime archive exceeds the custom E2B endpoint's upload limit and fails with HTTP 413 before build submission. Upload the unchanged archive as standard SDK COPY files of at most 32 MiB, concatenate them in the template, and verify SHA-256 before extraction.
Add explicit recovery of known upload-only failures using the original source SHA and template/build identifiers, with authenticated state checks. Retain nonsecret build receipts and upload checksums in artifacts on failure. Changes are confined to the fork's workflow and deployment documentation; no active template or service configuration changes.
Validation: actionlint, shellcheck, name guard (15 tests), CI-plan tests (36), and pinned SDK tests for chunk boundaries/order, reassembly, corruption rejection, empty archive rejection, recovery gates and receipts. Independent review passed. Cloud build validation follows merge; packaging readiness does not establish live Runtime execution qualification.