This is an automated email from the ASF dual-hosted git repository.
potiuk pushed a change to branch backport-dd9df35-v3-0-test
in repository https://gitbox.apache.org/repos/asf/airflow.git
discard 06c5cf8786d [v3-0-test] Add back missing `[sources]` link in generated
documentation's includes (#49978)
add 9a18b9f05c1 [v3-0-test] Implement offset to get the xcom for a given
task by offset. (#50011) (#50048)
add cd7cfa83ac0 [v3-0-test] Add back missing `[sources]` link in generated
documentation's includes (#49978)
This update added new revisions after undoing existing revisions.
That is to say, some revisions that were in the old version of the
branch are not in the new version. This situation occurs
when a user --force pushes a change and generates a repository
containing something like this:
* -- * -- B -- O -- O -- O (06c5cf8786d)
\
N -- N -- N refs/heads/backport-dd9df35-v3-0-test (cd7cfa83ac0)
You should already have received notification emails for all of the O
revisions, and so the following emails describe only the N revisions
from the common base, B.
Any revisions marked "omit" are not gone; other references still
refer to them. Any revisions marked "discard" are gone forever.
No new revisions were added by this update.
Summary of changes:
.../api_fastapi/execution_api/routes/xcoms.py | 30 +++--
.../execution_api/versions/head/test_xcoms.py | 81 +++++++++++++
.../tests/unit/models/test_mappedoperator.py | 12 +-
task-sdk/src/airflow/sdk/api/client.py | 36 ++++++
task-sdk/src/airflow/sdk/definitions/xcom_arg.py | 2 +-
task-sdk/src/airflow/sdk/execution_time/comms.py | 10 ++
.../airflow/sdk/execution_time/lazy_sequence.py | 103 ++++++++--------
.../src/airflow/sdk/execution_time/supervisor.py | 10 ++
.../task_sdk/execution_time/test_lazy_sequence.py | 131 +++++++++++++++++++++
.../task_sdk/execution_time/test_supervisor.py | 31 +++++
10 files changed, 386 insertions(+), 60 deletions(-)
create mode 100644 task-sdk/tests/task_sdk/execution_time/test_lazy_sequence.py
