Skip to content

Restore a vault with more than 64 objects - #1936

Closed
joepio wants to merge 2 commits into
developfrom
claude/project-thread-u8vgm0-vault-restore-batch
Closed

joepio wants to merge 2 commits into
developfrom
claude/project-thread-u8vgm0-vault-restore-batch

Conversation

@joepio

@joepio joepio commented Sep 30, 2026

Copy link
Copy Markdown
Member

Before: opening a drive on a new device and pressing "Restore from Cloud Vault" failed with "at most 64 objects per download-urls request" once the drive's vault held more than 64 objects, so the drive could not be restored at all.

After: the restore asks for download URLs in batches of 64 and restores the whole vault, in listing order as before.

How: restoreDrive in helpers/managed/vault.ts now requests /download-urls in chunks of DOWNLOAD_URL_BATCH (64, the control plane's MAX_URL_BATCH) and merges the answers. A new test restores 150 objects, checks the batches are 64/64/22, and fails without the fix with the production error.


Generated by Claude Code

download-urls signs at most 64 objects per request, and restoreDrive asked
for every object at once, so a drive with a longer history could not be
restored on a new device.
joepio added a commit that referenced this pull request Oct 1, 2026
…nt, Google sign-in (#1946)

Lands #1935 (server clock skew), #1936 (vault restore over 64 objects), #1944 (connect dialog), #1945 (twin agent resource) and #1856 (sign in to open the identity, pairs with atomic-saas #164), tested together on Mancave.

joepio commented Oct 1, 2026

Copy link
Copy Markdown
Member Author

Landed on develop through the batch #1946 (squash f2a07aa), tested together on Mancave. Closing this PR since its commits are in that batch.


Generated by Claude Code

@joepio joepio closed this Oct 1, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant