WIP: feat(transport): TUS upload for large attachments

[jpnurmi]

Note

Depends on:

• feat(transport): add HTTP retry with exponential backoff #1520

• Large attachments (>=100 MB) are stored as attachment-ref envelope items
• Database layer stores large attachment files separately in db/attachments/<uuid>/
• Transport layer streams each attachment-ref to the server via TUS before sending the envelope

See also:

• feat(server): Upload endpoint relay#5638
• feat(envelope): Attachment placeholder sentry-docs#16483
• https://develop.sentry.dev/sdk/telemetry/attachments/#attachment-placeholders
• https://develop.sentry.dev/sdk/telemetry/attachments/#attachment-placeholder-item

#skip-changelog (wip)

[jpnurmi]

@sentry review

[jpnurmi]

@cursor review

[jpnurmi]

@cursor review

[jpnurmi]

@cursor review

[cursor]

Debug function writes directly to stderr bypassing logging

Low Severity

The new debug_function added as a CURLOPT_DEBUGFUNCTION callback writes HTTP traffic details (headers, JSON bodies) directly to stderr via fprintf, bypassing the SDK's SENTRY_DEBUG/SENTRY_WARN logging infrastructure. Given the PR is titled "WIP", this appears to be development debugging code — it uses non-standard => / <= prefixes and selectively prints JSON-looking payloads, which is useful during development but inconsistent with the rest of the codebase.

 

[jpnurmi]

@cursor review

[cursor]

Cursor Bugbot has reviewed your changes and found 1 potential issue.

Bugbot Autofix prepared a fix for the issue found in the latest run.

• ✅ Fixed: copy_file_range fallback misses common filesystem errors
  • Expanded the copy_file_range fallback condition to also break on EXDEV, EOPNOTSUPP, and EINVAL so the read/write fallback handles these recoverable cases.

Or push these changes by commenting:

@cursor push 76476611c4

Preview (76476611c4)

diff --git a/src/path/sentry_path_unix.c b/src/path/sentry_path_unix.c
--- a/src/path/sentry_path_unix.c
+++ b/src/path/sentry_path_unix.c
@@ -362,7 +362,8 @@
             goto done;
         } else if (errno == EAGAIN || errno == EINTR) {
             continue;
-        } else if (errno == ENOSYS) {
+        } else if (errno == ENOSYS || errno == EXDEV || errno == EOPNOTSUPP
+            || errno == EINVAL) {
             break;
         } else {
             rv = 1;

_{This Bugbot Autofix run was free. To enable autofix for future PRs, go to the Cursor dashboard.}

[cursor]

copy_file_range fallback misses common filesystem errors

Medium Severity

The copy_file_range loop only falls through to the read/write fallback on ENOSYS. Other recoverable errors like EXDEV (cross-filesystem, common on Linux < 5.19), EOPNOTSUPP (filesystem doesn't support it), and EINVAL are treated as fatal failures, causing sentry__path_copy to return an error when the read/write loop would have succeeded. Since this function copies user-owned attachments into the database directory, cross-filesystem scenarios are realistic.