Remove false warning when TI state is QUEUED and TI doesn't have a start_date #34589
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.
closes: #34493
Airflow changes the TI state to queue in two cases:
airflow/airflow/jobs/backfill_job_runner.py
Line 533 in 7a5b6a3
airflow/airflow/jobs/scheduler_job_runner.py
Lines 603 to 614 in 7a5b6a3
and in both cases, TI may not have a start date if it's the first attempt, so the warning raised by
emit_state_change_metricmethod is false, and should be suppressed.