Repository navigation
c0mpute edge: mirror c0mpute 0.3.7 site size limits in verified reads - #36
Merged
Merged
Conversation
c0mpute #222 (v0.3.7) raised site.rs limits for media-size sites; the edge still refused anything over 1 GiB from an untrusted gateway. - MAX_SITE_BYTES 1 GiB -> 4 TiB (v2 record size, inline total, parted root) - v1 records capped at MAX_FREE_SITE_BYTES (64 GiB), as check_fields does - MAX_PARTS = ceil(MAX_FILES/PART_FILES) + 2*ceil((MAX_SITE_BYTES/FILE_CHUNK_BYTES)/PART_CHUNKS) + 2 = 2630 MAX_FILE_BYTES (128 GiB) is a publish-time check only, not a parse rule, so it is not mirrored. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
vu1nz Security Review0 finding(s) in PR #? No security issues found. |
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.
lib/c0mpute-verify.ts(#35) mirrors c0mputehosting/site.rs, whose limits changed in profullstack/c0mpute#222 (v0.3.7). Until now the edge refused any site over 1 GiB from an untrusted gateway.MAX_SITE_BYTES1 GiB -> 4 TiB: v2 recordsize, v1 inline manifest total, v2 rootbytesMAX_FREE_SITE_BYTES(64 GiB), matchingSiteRecord::check_fields(cap = v >= 2 ? MAX_SITE_BYTES : MAX_FREE_SITE_BYTES)MAX_PARTS= ceil(MAX_FILES/PART_FILES) + 2*ceil((MAX_SITE_BYTES/FILE_CHUNK_BYTES)/PART_CHUNKS) + 2 = 2630 (was 2500), since parts now also close atPART_CHUNKS= 65536 chunksChecked the rest of the #222 diff to site.rs:
MAX_FILE_BYTES(128 GiB),MAX_SMALL_SITE_BYTESandSTRIPE_ABOVEare publish/encode-time only, not parse or verification rules, so they are not mirrored. site.rs is unchanged since #222 (v0.3.8 did not touch it).Tests: a 3 GiB v2 site verifies end to end; a root at 2630 parts verifies and 2631 is refused; a v2 record at 4 TiB passes, 4 TiB + 1 fails; a v1 record at 64 GiB passes, +1 fails.
npm test: 134/134 pass.🤖 Generated with Claude Code