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
Four fixes found by auditing the implementation against spec PR #365:
- Unsupported _format → 400 (was 415 on the sof-server body path):
SofError::UnsupportedContentType now maps to ServerError::BadRequest,
per the spec's "SHALL be rejected with 400 Bad Request +
OperationOutcome". The stub tests that entrenched 415 are corrected,
and a new in-bin test locks the 400 against the production handler.
- _format=json export shards are now downloaded with
Content-Type: application/json (previously fell through to the
ndjson branch); test asserts the header.
- Export cancellation race: a job cancelled mid-run could be
resurrected to Completed/Failed by its background task, making
post-DELETE polls return 200 instead of the spec-required 404.
Completion/failure/progress writebacks now go through
set_status_if_running, which leaves a Cancelled job untouched.
Deterministic unit test added using a blocking mock SofRunner.
- HFS_EXPORT_PRESIGN_TTL_SECS default raised 3600 → 86400 so
out-of-the-box S3 deployments honor the spec's >= 24h
output.location validity (matching the Expires header already
advertised on the completion poll).
0 commit comments