Repository navigation
Conversation
Synchronous retries can submit another billable Message Batch after worker loss. Reconnecting to the saved batch keeps retries on the original remote work while preserving existing deferrable and no-wait behavior. Generated-by: GitHub Copilot CLI (GPT-5.6 Sol) Signed-off-by: 1fanwang <[email protected]>
The Airflow 3.2 compatibility path calls methods supplied by the concrete operator, which left the resumability change valid at runtime but rejected by MyPy. Generated-by: GitHub Copilot CLI (GPT-5.6 Sol) Signed-off-by: 1fanwang <[email protected]>
A canceled batch cannot produce a complete result, so reconnecting on retry can skip the task or return only a subset of requests. Generated-by: GitHub Copilot CLI (GPT-5.6 Sol) Signed-off-by: 1fanwang <[email protected]>
6c86890 to
4c8e75d
Compare
potiuk
added
the
closed because of open PR limit
|
Hello @1fanwang - 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 34 open pull requests, so - as a one-time step of introducing the limit - we closed the ones where maintainers have not engaged yet:
These pull requests stay open because maintainers are already engaged in them - they count towards your limit:
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 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 |
Synchronous
AnthropicBatchOperatorretries can submit a second billable Message Batch after a worker exits while polling. The batch ID is available through XCom, but Airflow clears XCom before the retry, so the next attempt cannot reconnect.On Airflow 3.3+, synchronous waits now persist the batch ID through
ResumableJobMixin. A retry reconnects to anin_progressbatch or returns a completed successful batch without another submission. It submits fresh work when the stored batch is missing, failed, expired, canceling, or contains canceled requests. Deferrable execution andwait_for_completion=Falseretain their current behavior.Testing
The regression drives two attempts through the real operator with a local task-state backing and mocked Anthropic API. On
upstream/main, the retry submits twice. This branch reconnects to the first batch.upstream/mainwith this PR's regression testcreate_batchcalled twiceRaw retry regression
Provider suites
Was generative AI tooling used to co-author this PR?
Generated-by: GitHub Copilot CLI (GPT-5.6 Sol) following the guidelines