The GitHub Actions job "Tests (AMD)" on airflow.git/fix/reschedule-rendered-map-index has failed. Run started by GitHub user kalluripradeep (triggered by kalluripradeep).
Head commit for run: c338c62d0d93629f1fea0c45f95d4a45c1f8b550 / Pradeep Kalluri <[email protected]> fix: propagate rendered_map_index through the reschedule state path When a sensor or operator raises ``AirflowRescheduleException`` from a mapped task, the ``map_index_template`` rendering must survive the supervisor ↔ scheduler round-trip so the UI shows a human-readable label (e.g. ``item-3``) on every *up_for_reschedule* row instead of the raw integer. Changes: * ``TIRescheduleStatePayload`` (data-model + task-SDK generated client) grows an optional ``rendered_map_index`` field. * ``task_runner.py`` populates it from ``ti.rendered_map_index`` before sending the ``RescheduleTask`` supervisor message. * ``supervisor.py`` captures it in ``_rendered_map_index`` in both the ``_send_terminal_state_msg`` fast-path and the ``_handle_request`` path. * The execution-API route persists the value via ``_rendered_map_index=ti_patch_payload.rendered_map_index`` in the bulk UPDATE query for ``UP_FOR_RESCHEDULE``. * A Cadwyn ``VersionChange`` (``AddRenderedMapIndexToReschedulePayload``) strips the field for older API clients. * ``schema.json`` supervisor-wire-protocol snapshot updated. * Regression test added in ``test_task_runner.py``. closes: #67521 Report URL: https://github.com/apache/airflow/actions/runs/28032111067 With regards, GitHub Actions via GitBox --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
