Skip to content

Bound large Gmail downloads and Drive upload transfers - #40

Merged
alexeygrigorev merged 1 commit into
mainfrom
fix/large-google-attachments
Nov 4, 2026
Merged

alexeygrigorev merged 1 commit into
mainfrom
fix/large-google-attachments

Conversation

@alexeygrigorev

Copy link
Copy Markdown
Member

Large Gmail attachments exceeded the Lambda JSON response contract, and large Drive uploads had the same base64 ingress problem. The CLI now downloads bounded Gmail ranges with whole-file SHA256 and atomic output, while Drive uses metadata-only initiation and a scoped Google resumable session with final checksum and account readback. Existing safe full Gmail responses and small Drive uploads remain supported. Validation: 64 focused API/CLI/provider tests passed, covering bounded wrappers, corrupted or changed chunks, destination preservation, safe session URLs, expiry, uncertain transfer status recovery, and end-to-end transport. Full tests and deployment run through CI. No production uploads or credential changes performed.

@alexeygrigorev
alexeygrigorev merged commit 41a9b10 into main Nov 4, 2026
24 of 26 checks passed
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