-
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鈥檒l occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix example timetable for AIP-39 howto #18475
Fix example timetable for AIP-39 howto #18475
Conversation
@@ -54,7 +54,7 @@ def next_dagrun_info( | |||
) -> Optional[DagRunInfo]: | |||
if last_automated_data_interval is not None: # There was a previous run on the regular schedule. | |||
last_start = last_automated_data_interval.start | |||
last_start_weekday = 7 - last_start.weekday() | |||
last_start_weekday = last_start.weekday() |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
馃う
fb19320
to
5eedd50
Compare
This makes the DAG "work" out of the box, which makes more sense.
5eedd50
to
00ffe5e
Compare
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. |
The wonderful QA team caught me doing stupid things. This fixes that. Plus:
dag_id
andstart_date
to the example DAG. This was also suggested by the QA team.