Skip to content

Conversation

@hussein-awala
Copy link
Member

closes: #34493

Airflow changes the TI state to queue in two cases:

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_metric method is false, and should be suppressed.

Comment on lines +2168 to +2169
# this could happen when the scheduler queue a TI
# or when the backfill CLI send a TI to the executor
Copy link
Member

@uranusjr uranusjr Sep 27, 2023

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Would it be a good idea for those cases to set the start date, or do a proactive filter to not call this function if the start date is None instead?

@hussein-awala
Copy link
Member Author

I close it in favor of #34771.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

emit_state_change_metric produces many warnings even in standard use cases

2 participants