This is an automated email from the ASF dual-hosted git repository.

uranusjr pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/airflow.git


The following commit(s) were added to refs/heads/main by this push:
     new bbcb63b4156 Indent todo comment for IDE highlighting compatibility 
(#58174)
bbcb63b4156 is described below

commit bbcb63b41563d2f98e0911968423fe73297cc041
Author: Daniel Standish <[email protected]>
AuthorDate: Mon Nov 10 18:29:32 2025 -0800

    Indent todo comment for IDE highlighting compatibility (#58174)
---
 airflow-core/src/airflow/jobs/scheduler_job_runner.py | 12 ++++++------
 1 file changed, 6 insertions(+), 6 deletions(-)

diff --git a/airflow-core/src/airflow/jobs/scheduler_job_runner.py 
b/airflow-core/src/airflow/jobs/scheduler_job_runner.py
index bb81fcbf7a0..f5fbc0acf61 100644
--- a/airflow-core/src/airflow/jobs/scheduler_job_runner.py
+++ b/airflow-core/src/airflow/jobs/scheduler_job_runner.py
@@ -1837,12 +1837,12 @@ class SchedulerJobRunner(BaseJobRunner, LoggingMixin):
                 and dag_run.clear_number < 1
             ):
                 # TODO: Logically, this should be DagRunInfo.run_after, but the
-                # information is not stored on a DagRun, only before the actual
-                # execution on DagModel.next_dagrun_create_after. We should add
-                # a field on DagRun for this instead of relying on the run
-                # always happening immediately after the data interval.
-                # We only publish these metrics for scheduled dag runs and only
-                # when ``run_type`` is *MANUAL* and ``clear_number`` is 0.
+                #  information is not stored on a DagRun, only before the 
actual
+                #  execution on DagModel.next_dagrun_create_after. We should 
add
+                #  a field on DagRun for this instead of relying on the run
+                #  always happening immediately after the data interval.
+                #  We only publish these metrics for scheduled dag runs and 
only
+                #  when ``run_type`` is *MANUAL* and ``clear_number`` is 0.
                 expected_start_date = get_run_data_interval(dag.timetable, 
dag_run).end
                 schedule_delay = dag_run.start_date - expected_start_date
                 # Publish metrics twice with backward compatible name, and 
then with tags

Reply via email to