This is an automated email from the ASF dual-hosted git repository.

pierrejeambrun pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/airflow.git


The following commit(s) were added to refs/heads/main by this push:
     new b2cae5d9950 Drop the stale RFC 9457 TODO on the task-instance-run 
endpoint (#71552)
b2cae5d9950 is described below

commit b2cae5d9950ae2962b4757df49e741ba96da1e14
Author: Pierre Jeambrun <[email protected]>
AuthorDate: Thu Aug 20 10:45:09 2026 +0200

    Drop the stale RFC 9457 TODO on the task-instance-run endpoint (#71552)
    
    The whole execution API returns errors as ``{"reason": ..., "message":
    ..., ...extras}`` — that shape is the de-facto contract now (parsed by
    the task SDK client at ``sdk/api/client.py``) and is applied uniformly
    across every route in the module. This TODO predates that convention
    and calling it out only on one 409 site is misleading: any single-
    endpoint migration to RFC 9457 would break the SDK parser and leave
    every other endpoint on the existing shape.
    
    Removing the comment so it stops attracting drive-by "fix RFC 9457"
    PRs; a real migration would need to be a cross-cutting change of the
    whole execution API plus the SDK parsers.
    
    related: #69360
---
 .../src/airflow/api_fastapi/execution_api/routes/task_instances.py   | 5 -----
 1 file changed, 5 deletions(-)

diff --git 
a/airflow-core/src/airflow/api_fastapi/execution_api/routes/task_instances.py 
b/airflow-core/src/airflow/api_fastapi/execution_api/routes/task_instances.py
index 02d723a8218..123f56c1f10 100644
--- 
a/airflow-core/src/airflow/api_fastapi/execution_api/routes/task_instances.py
+++ 
b/airflow-core/src/airflow/api_fastapi/execution_api/routes/task_instances.py
@@ -221,11 +221,6 @@ def ti_run(
             previous_state=previous_state,
         )
 
-        # TODO: Pass a RFC 9457 compliant error message in "detail" field
-        # https://datatracker.ietf.org/doc/html/rfc9457
-        # to provide more information about the error
-        # FastAPI will automatically convert this to a JSON response
-        # This might be added in FastAPI in 
https://github.com/fastapi/fastapi/issues/10370
         raise HTTPException(
             status_code=status.HTTP_409_CONFLICT,
             detail={

Reply via email to