Add fastAPI test coverage for upstream_map_indexes in execution API #50541

Activity

1. amoghrajesh

   added

   area:APIAirflow's REST/HTTP APIAirflow's REST/HTTP API

   kind:metaHigh-level information important to the communityHigh-level information important to the community

   area:task-execution-interface-aip72AIP-72: Task Execution Interface (TEI) aka Task SDKAIP-72: Task Execution Interface (TEI) aka Task SDK

   and removed

   kind:metaHigh-level information important to the communityHigh-level information important to the community

   on May 13, 2025
2. amoghrajesh

   assigned

   sunank200

   on May 13, 2025
3. anasatzemoso commented on Sep 18, 2025

   

   anasatzemoso

   on Sep 18, 2025

   Contributor

   More actions

   Can I work on this issue ?
4. anasatzemoso commented on Sep 19, 2025

   

   anasatzemoso

   on Sep 19, 2025

   Contributor

   More actions

   I looked into this and found that there’s already a parameterized test (test_ti_run) for the /execution/task-instances/{ti.id}/run endpoint. It patches _get_upstream_map_indexes and asserts that the upstream_map_indexes field is returned in the response with the expected structure across multiple scenarios (ints, lists, None, mixed types).

   This seems to cover the gap mentioned in the issue — verifying that the field is returned correctly in the API response. Could you confirm if this is the intended scope, or if there’s anything additional expected here?
5. sunank200

   removed their assignment

   on Feb 20, 2026
6. bintocher

   added a commit that references this issue on Feb 21, 2026

   fix: add test for upstream_map_indexes not in HEAD API response

   ...

   This issue will close once commit ce073fd is merged into the 'main' branch.

   ce073fd
7. bintocher

   added 2 commits that reference this issue on Mar 4, 2026

   fix: add test for upstream_map_indexes not in HEAD API response

   ...

   This issue will close once commit 9b81330 is merged into the 'main' branch.

   9b81330

   fix: add test for upstream_map_indexes not in HEAD API response

   ...

   This issue will close once commit 1baa508 is merged into the 'main' branch.

   1baa508
8. potiuk

   closed this as completedin f1cb407on Mar 11, 2026
9. kaxil

   added a commit that references this issue on Mar 11, 2026

   fix: add test for upstream_map_indexes not in HEAD API response (apac…

   ...

   This issue will close once commit f1cb407 is merged into the 'main' branch.

   f1cb407
10. dominikhei

    added a commit that references this issue on Mar 11, 2026

    fix: add test for upstream_map_indexes not in HEAD API response (apac…

    ...

    This issue will close once commit 9814fa4 is merged into the 'main' branch.

    9814fa4
11. PascalEgn

    added a commit that references this issue on Mar 12, 2026

    fix: add test for upstream_map_indexes not in HEAD API response (apac…

    ...

    This issue will close once commit 923f3af is merged into the 'main' branch.

    923f3af
12. Pyasma

    added a commit that references this issue on Mar 13, 2026

    fix: add test for upstream_map_indexes not in HEAD API response (apac…

    ...

    This issue will close once commit 29daa70 is merged into the 'main' branch.

    29daa70
13. kosteev

    added a commit that references this issue on Aug 3, 2026

    fix: add test for upstream_map_indexes not in HEAD API response (#62283)

    ...

    This issue will close once commit d4312f6 is merged into the 'main' branch.

    d4312f6
14. kosteev

    added a commit that references this issue on Sep 12, 2026

    fix: add test for upstream_map_indexes not in HEAD API response (#62283)

    ...

    This issue will close once commit 8d74c30 is merged into the 'main' branch.

    8d74c30