test(python-sdk): regression tests for template upload Content-Length

[mishushakov]

Summary

• Adds sync + async regression tests for upload_file in template_sync / template_async. Both spin up a local HTTP server on 127.0.0.1:0, PUT the archive at it, and assert the request carries a Content-Length matching the body and does not use Transfer-Encoding: chunked.
• Guards against a future change swapping the buffered bytes (tar_buffer.getvalue()) for a generator/stream, which would trigger chunked encoding and break S3 presigned PUT uploads with 501 NotImplemented — the same class of bug that hit the JS SDK in fix(js-sdk): buffer template upload to avoid S3 chunked PUT 501 #1285 / [JS SDK] uploadFile uses chunked transfer encoding, causing 501 NotImplemented on S3 presigned PUT URLs #1243.

No Python SDK code changes — the current implementation already passes bytes to httpx.put(..., content=...), so this is purely a regression guard.

Test plan

• poetry run pytest tests/sync/template_sync/test_upload_file.py tests/async/template_async/test_upload_file.py -v — both pass locally
• poetry run make format / make lint / make typecheck clean

🤖 Generated with Claude Code

[cursor]

PR Summary

Low Risk
Low risk because changes are test-only and don’t modify runtime SDK behavior; they primarily guard against a future regression that would break presigned PUT uploads.

Overview
Adds sync and async regression tests for template_* upload_file that PUT to a local HTTP server and assert the request includes a non-zero Content-Length matching the received body.

The tests also assert the upload does not use Transfer-Encoding: chunked, protecting against future refactors that might switch the request body to a stream/generator and break S3 presigned PUT URLs.

^{Reviewed by Cursor Bugbot for commit bc3f865. Bugbot is set up for automated code reviews on this repo. Configure here.}

[changeset-bot]

⚠️ No Changeset found

Latest commit: bc3f865

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[github-actions]

Package Artifacts

Built from 3155e27. Download artifacts from this workflow run.

JS SDK (e2b@2.19.1-mishushakov-py-upload-tests.0):

npm install ./e2b-2.19.1-mishushakov-py-upload-tests.0.tgz

CLI (@e2b/cli@2.9.1-mishushakov-py-upload-tests.0):

npm install ./e2b-cli-2.9.1-mishushakov-py-upload-tests.0.tgz

Python SDK (e2b==2.20.0+mishushakov-py-upload-tests):

pip install ./e2b-2.20.0+mishushakov.py.upload.tests-py3-none-any.whl

[claude]

Test-only regression guard for upload_file Content-Length behavior — straightforward and self-contained.

Extended reasoning...

Overview

This PR adds two new test files (sync + async) under packages/python-sdk/tests/ that spin up a local HTTPServer on 127.0.0.1:0, invoke upload_file against it, and assert the request carries a matching Content-Length and no Transfer-Encoding: chunked. No runtime SDK code is modified.

Security risks

None. Tests bind to loopback only, use ephemeral ports, and run in daemon threads that are torn down in a finally block. No credentials, network egress, or filesystem writes outside pytest's tmp_path.

Level of scrutiny

Low. This is a pure test addition guarding against a previously-seen class of bug (JS SDK #1285/#1243 where presigned S3 PUTs failed under chunked encoding). The tests exercise the public function signature and assert on observable HTTP behavior — no mocking of internals, no brittle coupling.

Other factors

The mock server pattern is simple and correct: server.shutdown() + server_close() + thread.join(timeout=5) in finally ensures cleanup even on failure. The async test correctly relies on the fact that the sync HTTPServer in a daemon thread does not block the asyncio event loop, since httpx.AsyncClient uses asyncio sockets to talk to it. The assertions are precise (Content-Length > 0, matches received body length, no chunked TE) and fail-loud.