Add regression test for streaming proxy body #59

New issue

Open

opened 2026-04-26 07:47:41 +00:00 by zaelgohary · 0 comments

zaelgohary commented

2026-04-26 07:47:41 +00:00

Member

service_proxy_* streams the request body to the backend UDS without buffering. There is no in-repo test that locks this in — a future refactor that reintroduces to_bytes(body, LIMIT) would silently bring back the upload ceiling.

Acceptance

A test (under crates/hero_router/tests/ or a new integration test) that:
- Stands up a tmp UDS-backed echo / sink server inside the test process.
- Routes a multi-MB PUT through hero_router to that backend.
- Asserts the backend received the full body intact (correct length, optional sha256 round-trip).
Test is fast enough to run in CI (e.g. 50 MB upload, not 1 GB).

`service_proxy_*` streams the request body to the backend UDS without buffering. There is no in-repo test that locks this in — a future refactor that reintroduces `to_bytes(body, LIMIT)` would silently bring back the upload ceiling. ## Acceptance - A test (under `crates/hero_router/tests/` or a new integration test) that: - Stands up a tmp UDS-backed echo / sink server inside the test process. - Routes a multi-MB PUT through hero_router to that backend. - Asserts the backend received the full body intact (correct length, optional sha256 round-trip). - Test is fast enough to run in CI (e.g. 50 MB upload, not 1 GB).