Skip to content

Respond to PR check-in comment#1016

Closed
Copilot wants to merge 17 commits into
multipart-improvementsfrom
copilot/sub-pr-1012
Closed

Respond to PR check-in comment#1016
Copilot wants to merge 17 commits into
multipart-improvementsfrom
copilot/sub-pr-1012

Conversation

Copilot AI commented Jan 9, 2026

Copy link
Copy Markdown
Contributor

Acknowledged availability in response to @LeMikaelF's check-in comment on the multipart upload improvements PR. No code changes were required as all existing comment threads are either resolved or informational.


💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.

LeMikaelF and others added 17 commits January 9, 2026 09:11
  When users upload databases >1GB while authenticated with a JWT token,
  show a warning that JWTs are short-lived and may expire during long
  transfers. Recommend using API tokens instead and show how to create one.

  The warning can be skipped with --yes flag or by setting TURSO_API_TOKEN.
  When importing large database files with `turso db import`, the SQLite
  validation step (pragma quick_check) would make the CLI appear hung.
  This adds a spinner with percentage progress during validation.

  - Use sqlite3's `.progress N` command to get periodic callbacks
  - Dynamically adjust callback interval based on file size (~100 updates)
  - Cap progress at 99% until validation completes (estimate may overshoot)
  - Add SpinnerInterface for testability
  - Add comprehensive tests for the new functionality

  🤖 Generated with [Claude Code](https://claude.com/claude-code)

  Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
  Instead of hardcoding a 1-hour expiration for upload tokens, calculate
  the expiration based on file size assuming 10 MB/s minimum upload speed
  plus a 1-hour buffer for server-side validation.

  This fixes uploads failing mid-transfer for large databases (e.g., 93GB)
  when the 1-hour token expires before the upload completes.

  Also removes the misleading JWT expiration warning that suggested using
  API tokens, since the upload always creates a JWT regardless of how
  the user authenticated.
Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
Chunks now retry up to 3 times with exponential backoff on transient
failures (5xx, network errors, 408, 429). Token is refreshed on each
retry attempt to prevent expiration during long retry sequences.

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
@LeMikaelF

Copy link
Copy Markdown
Contributor

@copilot Look at the CI failure on the target branch, it should be fixed by a previous merged PR (#1015). Why is the CI action still using 1da86b1d3e6944a00c18d525f2dfba006f4cbd6c (the old version) instead of b53ecaccb94623dfa6050e4ada4eeecd3a130829 (the new version)?

Copilot AI changed the title [WIP] Improve multipart upload flow with various enhancements Respond to PR check-in comment Jan 9, 2026
Copilot AI requested a review from LeMikaelF January 9, 2026 19:43

Copilot AI commented Jan 9, 2026

Copy link
Copy Markdown
Contributor Author

@copilot Look at the CI failure on the target branch, it should be fixed by a previous merged PR (#1015). Why is the CI action still using 1da86b1d3e6944...

The CI is using the old version because the multipart-improvements branch (the target branch for this PR) hasn't been updated with the fix from PR #1015 yet.

PR #1015 was merged to main on 2026-01-09 and updated the commit hash to b53ecaccb94623dfa6050e4ada4eeecd3a130829, but multipart-improvements was branched off before that merge. To fix the CI failure, you'll need to merge or rebase main into multipart-improvements to pick up the sqlclosecheck fix.

@LeMikaelF

Copy link
Copy Markdown
Contributor

This is a dummy PR. I tagged copilot and it opened a PR, I used it just for discussing my problem and it spotted the issue.

@LeMikaelF LeMikaelF closed this Jan 9, 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.

2 participants