Conversation
XYenon
marked this pull request as ready for review
June 1, 2026 11:30
XYenon
force-pushed
the
feat/chunked-upload
branch
from
June 15, 2026 07:49
b30f058 to
74a031a
Compare
XYenon
force-pushed
the
feat/chunked-upload
branch
4 times, most recently
from
June 28, 2026 09:04
b997c10 to
97b4135
Compare
Add chunked transport upload sessions for pushing large NARs. Clients can upload a NAR as sequential transport parts, and the server stores those parts in temporary upload sessions before ingesting the reconstructed NAR. Expose chunked upload capability through cache-config when the server configures upload.max-chunk-size. Clients use non-chunked uploads when the capability is absent, use the advertised max chunk size by default when present, and reject explicit --chunk-size values that exceed the server limit. Finalize upload sessions asynchronously and let clients poll for completion. The server waits until all expected parts are present before starting finalization, then validates part ordering and size, ingests the reconstructed NAR, records the result, and cleans up temporary session parts. Add upload session database entities, migrations, API routes, and garbage collection for stale session data. Amp-Thread-ID: https://ampcode.com/threads/T-019e8181-6abd-750d-a9c6-42d48108a529 Co-authored-by: Amp <amp@ampcode.com>
Amp-Thread-ID: https://ampcode.com/threads/T-019e8181-6abd-750d-a9c6-42d48108a529 Co-authored-by: Amp <amp@ampcode.com>
XYenon
force-pushed
the
feat/chunked-upload
branch
from
July 16, 2026 16:33
97b4135 to
fe8e54d
Compare
Co-authored-by: factory-droid[bot] <138933559+factory-droid[bot]@users.noreply.github.com>
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.
Add chunked transport upload sessions for pushing large NARs. Clients can upload a NAR as sequential transport parts, and the server stores those parts in temporary upload sessions before ingesting the reconstructed NAR.
Expose chunked upload capability through cache-config when the server configures upload.max-chunk-size. Clients use non-chunked uploads when the capability is absent, use the advertised max chunk size by default when present, and reject explicit --chunk-size values that exceed the server limit.
Finalize upload sessions asynchronously and let clients poll for completion. The server waits until all expected parts are present before starting finalization, then validates part ordering and size, ingests the reconstructed NAR, records the result, and cleans up temporary session parts.
Add upload session database entities, migrations, API routes, and garbage collection for stale session data.
Closes #287.