Jeroen UbbinkandClaude Opus 5 09e356b642 fix(api): answer a request-validation failure with a 422 that serializes ...

`json` parses the bare `Infinity`/`NaN` literals into real floats, so the
pricing edge rejects them correctly — but pydantic echoes the offending value
back in the error's `input` field, and JSONResponse encodes with
`allow_nan=False`. Serializing the 422 then raised "Out of range float values
are not JSON compliant" and the reply escaped as a 500, reporting a client's bad
rate as a server fault. The request already failed closed, so no row was ever
written.

Handle RequestValidationError explicitly and render non-finite floats as text,
which covers every endpoint rather than the pricing edge alone. The integration
app now copies the main app's exception handlers so a failing request fails the
way it does in production.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_011cKHVF5LA7TR5QuYi6ErLM

2026-08-25 16:23:31 +02:00

..

integration

fix(api): answer a request-validation failure with a 422 that serializes

2026-08-25 16:23:31 +02:00

unit

fix(pricing): treat a non-finite rate as no price wherever pricing is ingested

2026-08-25 16:16:15 +02:00

conftest.py

test: add return type annotations to cache fixtures for strict mypy

2026-08-17 23:26:52 +02:00

run_integration.py

dump wip stash

2025-08-06 20:31:55 -03:00