Repository navigation
feat: add resumable upload - #2
Merged
Merged
Conversation
Syrup
added a commit
that referenced
this pull request
Oct 13, 2026
* feat: add resumable upload * feat(resume): add upload state model * test(resume): fix upload state timestamp assertion * feat(resume): record upload progress * test(resume): cover mid-upload failure state * feat(resume): complete interrupted upload resume
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.
Summary
Add resumable uploads for interrupted backup runs.
This now uses per-chunk age encryption instead of one full encrypted payload. Resume can re-read the original source file, skip chunks already recorded in local upload state, upload missing chunks, then finalize the backup with
manifest.ageandlocator.json.What changed
gloak resume <backup-id>.~/.gloak/uploads/<backup-id>.json.Why per-chunk encryption
Age recipient encryption is randomized, so re-encrypting a whole file from the beginning does not reproduce the same ciphertext chunks. Per-chunk encryption avoids that problem. Resume compares plaintext chunk hashes from the source file against the saved state, then uploads only missing chunks.
Testing
go test ./...go build ./...