You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@airflow.apache.org by "bujjibabukatta (via GitHub)" <gi...@apache.org> on 2026/08/05 16:24:30 UTC
[PR] Surface hasMappedDependants on ts-sdk TaskContext [airflow]
bujjibabukatta opened a new pull request, #71191:
URL: https://github.com/apache/airflow/pull/71191
Adds `TaskContext.hasMappedDependants` to the TypeScript SDK, mirroring
the `should_retry` field pattern already used for TIRunContext →
TaskContext mapping.
When `true`, returning an array from a task handler causes the
supervisor to record `mapped_length` on the return-value XCom
automatically, letting the scheduler expand downstream mapped
dependants — matching behavior already available to Python task
handlers.
Changes:
* `ts-sdk/src/sdk/task.ts` — add `readonly hasMappedDependants: boolean`
to the public `TaskContext` interface
* `ts-sdk/src/coordinator/runtime.ts` — wire `ti_context.has_mapped_dependants`
into `buildContext()`, defaulting to `false` when the server omits it
* `ts-sdk/tests/coordinator/integration.test.ts` — cover both the
`true` and default-`false` cases end-to-end through the coordinator
* `ts-sdk/tests/coordinator/client.test.ts`, `ts-sdk/tests/public-api.test.ts` —
update existing `TaskContext` fixtures/type assertions for the new
required field
Depends on `has_mapped_dependants` existing on `TIRunContext`
(#70571) — rebased onto that once merged, `schema.json` /
`supervisor.ts` regeneration is a no-op beyond the one field.
closes: #71063
##### Was generative AI tooling used to co-author this PR?
- [X] Yes (Claude)
- Used for PR description and test cases
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@airflow.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [PR] Surface hasMappedDependants on ts-sdk TaskContext [airflow]
Posted by "potiuk (via GitHub)" <gi...@apache.org>.
potiuk closed pull request #71191: Surface hasMappedDependants on ts-sdk TaskContext
URL: https://github.com/apache/airflow/pull/71191
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@airflow.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
Re: [PR] Surface hasMappedDependants on ts-sdk TaskContext [airflow]
Posted by "potiuk (via GitHub)" <gi...@apache.org>.
potiuk commented on PR #71191:
URL: https://github.com/apache/airflow/pull/71191#issuecomment-5839267597
Hello @bujjibabukatta - thank you for your contributions to Apache Airflow!
The Airflow community has introduced a limit of **5 open pull requests at a time** for contributors without write access to the repository. You currently have 16 open pull requests, so - as a one-time step of introducing the limit - we closed the ones where maintainers have not engaged yet:
* #70584 - Fix airflowctl always using production creds when --env is passed
* #70712 - Skip redundant dag.exceeds_max_non_backfill writes to reduce scheduler/DAG-processor lock contention
* #70781 - Allow temporal partition mappers to accept already-normalized keys
* #71052 - Skip file-based dag processor logs when dag_processor_log_target=stdout
* #71064 - Add opt-in append_blob write mode for WASB task logs
* #71114 - deny unknown backfill_id directly instead of falling back to body dag_id
* #71166 - Fix DAG processor treating non-.zip files as DAG bundles (#71125)
* #71191 - Surface hasMappedDependants on ts-sdk TaskContext
* #71673 - fix: FAB get_application_builder should use create_metadata_engine hook
* #72556 - Task SDK: Fix executor_config aliasing across tasks sharing default_args
* #72879 - Add job_name support to DataflowJobStatusSensor and DataflowJobStatusTrigger
These pull requests stay open because maintainers are already engaged in them - they count towards your limit:
* #70635 - fix(amazon): include deferred-task trigger logs when reading from Clo…
* #70716 - Fix ReDoS in SparkSubmitHook._mask_cmd on adversarial input
* #70883 - Point mask_secret deprecation warning at the module it actually uses
* #70922 - Build DataprocCreateClusterOperator cluster_config from legacy kwargs after rendering
* #71480 - Anchor run_id to logical_date when create_cron_data_intervals is enab…
This is **not** a judgement of you or of your changes. We never told contributors before that opening many pull requests at once was a problem, so there is nothing to feel bad about - and nothing is lost: your branches, commits and the review history stay where they are.
What we ask you to do is to make your **first prioritization decision**: choose which of the pull requests above matter most to you, and reopen them (up to 5 open at a time, including the ones still open) with the "Reopen pull request" button or `gh pr reopen <PR_NUMBER> --repo apache/airflow`. Reopen the ones you are ready to follow through - keep them rebased, respond to review comments and fix failing checks.
While your pull requests are waiting for review, the most valuable thing you can do is help in other ways - reviewing other contributors' pull requests, helping with issues, and taking part in the discussions on the devlist and Slack.
Why we introduced the limit, what it means for you and how to reopen or restore a pull request is explained in https://github.com/apache/airflow/blob/main/contributing-docs/32_open_pull_request_limit.rst.
---
Drafted-by: Claude Code (Opus 5); reviewed by @potiuk before posting
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: commits-unsubscribe@airflow.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org