The GitHub Actions job "Check newsfragment PR number" on airflow.git/fix/db-data-error-actionable has failed. Run started by GitHub user 1fanwang (triggered by 1fanwang).
Head commit for run: 00c316a668674ef62113dc0e2945500c6d785207 / 1fanwang <[email protected]> Translate DataError to 413/422 instead of generic 500 Triggering a DAG run with an oversized 'conf' payload (and other DB-rejected writes across the API surface) currently produces a generic 500. The SQL error surfaces deep in SQLAlchemy as (1406, "Data too long for column 'conf' at row 1") on MySQL, the caller has no signal that payload size was the cause, and every write endpoint that touches a length-capped column has the same shape today (Connection.extra, Variable.val, XCom.value, TaskInstance.note, HITL fields, etc). Add a single FastAPI exception handler for sqlalchemy.exc.DataError on both the public REST API and the execution API. 'Data too long' / 'too large' / 'too big' errors map to 413 Content Too Large; other DataErrors (out-of-range, numeric overflow) map to 422. The response body carries the original DB error and an actionable hint pointing at either reducing the payload or widening the column type on MySQL. Every existing and future write endpoint inherits the translation automatically. Postgres deployments never hit it (JSONB has no length cap); MySQL deployments get a clear 4xx + remediation hint instead of a generic 500. Closes #66779 Signed-off-by: 1fanwang <[email protected]> Report URL: https://github.com/apache/airflow/actions/runs/25828569178 With regards, GitHub Actions via GitBox --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
