-
Notifications
You must be signed in to change notification settings - Fork 13.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix stray order_by(TaskInstance.execution_date) #21705
Fix stray order_by(TaskInstance.execution_date) #21705
Conversation
The PR most likely needs to run full matrix of tests because it modifies parts of the core of Airflow. However, committers might decide to merge it quickly and take the risk. If they don't merge it quickly - please rebase it to the latest main at your convenience, or amend the last commit of the PR, and push it with --force-with-lease. |
Thank you for fixing this! |
e96650b
to
6497ffb
Compare
Change looks good, but I thought this would work through theh association_proxy anyway? Obviously not by the error report |
|
(cherry picked from commit bb577a9)
(cherry picked from commit bb577a9)
(cherry picked from commit bb577a9)
(cherry picked from commit bb577a9)
(cherry picked from commit bb577a9)
(cherry picked from commit bb577a9)
(cherry picked from commit bb577a9)
(cherry picked from commit bb577a9)
Fix #21656.
Nobody noticed this exists because the function
BaseOperator.get_task_instances()
is not used anywhere in the code base. But since this is public API, we should still fix it.A quick search for
order_by(TaskInstance.execution_date)
andorder_by(TI.execution_date)
yielded no other results; this is probably the only one we missed.