You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
## Summary
- harden the split execution endpoints added in vllm-project#216 with validated
secret types, separate hydrate, context, response, and persist size
budgets, stable 401, 409, and 413 error envelopes, and propagated
shutdown errors
- make duplicate persistence atomic by mapping the database uniqueness
violation to a stable `409 response_already_stored` response
- strictly validate caller-relayed JSON and SSE response lifecycles,
required fields, item identity and type, terminal status, and permanent
output ID/index uniqueness before persistence
- treat `response.output_item.done` as authoritative so missing deltas
cannot silently truncate stored message content, and reject stream item
types that cannot be represented safely
- document the workload-token contract, deployment trust boundary,
limits, and retry behavior
The workload token authenticates a trusted coordinator, not a tenant.
Per-response tenant ownership remains tracked in vllm-project#107, so these
endpoints should stay on an encrypted, policy-restricted service
network.
## Test Plan
- `cargo fmt --all -- --check`
- `CARGO_INCREMENTAL=0 RUSTFLAGS='-C debuginfo=0' cargo clippy -j 2
--workspace --all-targets -- -D warnings`
- `CARGO_INCREMENTAL=0 RUSTFLAGS='-C debuginfo=0' cargo test --workspace
-j 2`
- `uv run --with-requirements docs/requirements.txt mkdocs build
--strict`
The standard PostgreSQL tests that require `TEST_POSTGRES_URL` remained
ignored.
---------
Signed-off-by: Francisco Javier Arceo <farceo@redhat.com>
0 commit comments