fix(scheduler): ignore queued stale success after defer - #67330
Closed
anmolxlight wants to merge 1 commit into
Closed
fix(scheduler): ignore queued stale success after defer#67330anmolxlight wants to merge 1 commit into
anmolxlight wants to merge 1 commit into
Conversation
potiuk
marked this pull request as draft
July 2, 2026 18:44
potiuk
marked this pull request as ready for review
July 2, 2026 22:15
Contributor
|
Hey @anmolxlight, looks like the diagnosis is right and this exact fix already landed in #68741 (merged Jul 2), which also closed #67287. That PR makes the same change to the I believe this PR can be closed now! |
Contributor
Author
|
Thanks @steveahnahn for catching that — confirmed that #68741 already addressed this. Closing this PR as superseded. 👋 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
TaskInstanceState.QUEUEDin addition toSCHEDULED.next_methodis set.Testing
uv run --project airflow-core pytest airflow-core/tests/unit/jobs/test_scheduler_job.py::TestSchedulerJob::test_process_executor_events_stale_success_when_rescheduled_after_defer -q --with-db-inituv run prek run ruff --files airflow-core/src/airflow/jobs/scheduler_job_runner.py airflow-core/tests/unit/jobs/test_scheduler_job.pyuv run prek run ruff-format --files airflow-core/src/airflow/jobs/scheduler_job_runner.py airflow-core/tests/unit/jobs/test_scheduler_job.pyCloses #67287
Important
🛠️ Maintainer triage note for @anmolxlight · by
@potiuk· 2026-07-02 22:14 UTCI've removed the
ready for maintainer reviewlabel because the next step here is yours:main. Please rebase onto the latestmainand resolve them.The ball is in your court — you've been assigned. It'll return to the maintainer queue automatically once you rebase and mark it Ready for review — no need to re-add the label by hand.
Automated triage — may be imperfect; a maintainer takes the next look.