Fix broken stat scheduler_loop_duration

[0vj00]

The stat scheduler_loop_duration is broken since this change. The nesting of the stats context statement results in it not capturing the full scheduler loop duration. This PR fixes the nesting.

---

^ Add meaningful description above
Read the Pull Request Guidelines for more information.
In case of fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
In case of a new dependency, check compliance with the ASF 3rd Party License Policy.
In case of backwards incompatible changes please leave a note in a newsfragment file, named {pr_number}.significant.rst or {issue_number}.significant.rst, in newsfragments.

[boring-cyborg]

Congratulations on your first Pull Request and welcome to the Apache Airflow community! If you have any issues or are unsure about any anything please check our Contributors' Guide (https://github.com/apache/airflow/blob/main/contributing-docs/README.rst)
Here are some useful points:

• Pay attention to the quality of your code (ruff, mypy and type annotations). Our pre-commits will help you with that.
• In case of a new feature add useful documentation (in docstrings or in docs/ directory). Adding a new operator? Check this short guide Consider adding an example DAG that shows how users should use it.
• Consider using Breeze environment for testing locally, it's a heavy docker but it ships with a working Airflow and a lot of integrations.
• Be patient and persistent. It might take some time to get a review or get the final approval from Committers.
• Please follow ASF Code of Conduct for all communication including (but not limited to) comments on Pull Requests, Mailing list and Slack.
• Be sure to read the Airflow Coding style.
• Always keep your Pull Requests rebased, otherwise your build might fail due to changes not related to your commits.
  Apache Airflow is a community-driven project and together we are making it better 🚀.
  In case of doubts contact the developers at:
  Mailing List: [email protected]
  Slack: https://s.apache.org/airflow-slack

[0vj00]

@howardyoo - I'd appreciate if you can review as well, since this follows up on your original PR #40802

[howardyoo]

Thanks, I’ll take a look!Sent from my iPhoneOn Oct 10, 2024, at 2:09 AM, Venkat VJ ***@***.***> wrote: @howardyoo - Would appreciate if you can review as well, since this follows up on your original PR #40802 —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: ***@***.***>

[potiuk]

I approved the run - @howardyoo, would be great to get the review. Also - if we could have some unit test for that (can we?) it would be great.

[howardyoo]

I approved the run - @howardyoo, would be great to get the review. Also - if we could have some unit test for that (can we?) it would be great.

I don't think this can be unit-tested..?
The fix seems to be related to some changes that happened outside of Airflow OTEL implementation, but the code change makes sense. So I'd say let's approve and merge it.

[boring-cyborg]

Awesome work, congrats on your first merged pull request! You are invited to check our Issue Tracker for additional contributions.

[sunchao]

@potiuk @0vj00 any chance this can be added to Airflow 2.10.3 release? we are seeing the same issue as well

[potiuk]

@potiuk @0vj00 any chance this can be added to Airflow 2.10.3 release? we are seeing the same issue as well

No. Not unless 2.10.3 rc1 is cancelled and we attempt to do 2.10.3rc2 (cc: @utkarsharma2 @ephraimbuddy ) -> I marked it provisionally for 2.10.4 - next time it's a good idea to mention it before we prepare a new release, that things are good candidates and would be great to back-port.

[sunchao]

I see, thanks @potiuk

[potiuk]

We are going to have rc2 - > backporting that one in #43544