Skip to content

feat(sdk): stream uploads from source files#16

Merged
pfwang80s merged 1 commit into
mainfrom
pfwang80s/direct-upload-streaming-reinit
Jun 14, 2026
Merged

feat(sdk): stream uploads from source files#16
pfwang80s merged 1 commit into
mainfrom
pfwang80s/direct-upload-streaming-reinit

Conversation

@pfwang80s

Copy link
Copy Markdown
Contributor

Summary

  • Upload prepared files directly from the original source URL instead of copying external files into managed staging.
  • Use file and stream request bodies for OSS upload paths, including multipart range streams, explicit Content-Length, and Content-MD5 without whole-file payload reads.
  • Keep security-scoped bookmark access active across upload, resume, checksum, and completion validation reads.
  • Automatically fall back to Qiongche device reinit when initialization reports that the device ID has already been initialized.
  • Expand local and online e2e coverage for direct source uploads, multipart streaming, resume, abort/delete, runtime upload events, and Qiongche initialization/upload flows.

Verification

  • git diff --check
  • swift test --filter QiongcheDataGatewaySDKTests (33 tests passed)
  • swift test (240 tests passed)
  • swift test --filter LocalStackHarnessTests against the dev deployment config from ../data-platform/_dev_aliyun_deploy.yaml (34 tests passed)
  • swift test --filter realAliyunListObjectsFlow against the same dev deployment (1 test passed)

Notes

  • The online e2e run used temporary test credentials and devices derived from the dev deployment configuration; no secrets are included in this PR.

@pfwang80s pfwang80s merged commit 0c13e2e into main Jun 14, 2026
1 check passed
@pfwang80s pfwang80s deleted the pfwang80s/direct-upload-streaming-reinit branch June 14, 2026 07:04
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