samraj2k opened a new pull request, #73717:
URL: https://github.com/apache/airflow/pull/73717

   ## Summary
   
   - Add a normalized `bundle_name` tag to `dag_processing.processor_timeouts` 
so timeouts for the same relative `file_path` in different Dag bundles are 
separate metric series.
   - Update the metric registry description and regression tests for bundle 
attribution, name normalization, and multi-team tagging.
   
   ## Local verification
   
   - `breeze run --skip-image-upgrade-check pytest 
airflow-core/tests/unit/dag_processing/test_manager.py -xq`: **177 passed, 5 
skipped, 1 warning**. The skipped tests require PostgreSQL; this run used 
SQLite.
   - `prek run --from-ref upstream/main --stage pre-commit`: passed, including 
Ruff, mypy, and the metrics registry check.
   - `prek run --from-ref upstream/main --stage manual --skip 
compile-ui-assets-dev --skip view-skill-eval --skip run-skill-eval-codex`: 
passed.
   - A controlled runtime probe exercised Airflow's processor timeout path 
through the configured StatsD backend and a local UDP receiver. For the same 
`file_path`, it captured:
   
     ```text
     
airflow.dag_processing.processor_timeouts,file_path=shared.py,bundle_name=bundle_alpha:1|c
     
airflow.dag_processing.processor_timeouts,file_path=shared.py,bundle_name=bundle_beta:1|c
     ```
   
   The Breeze tests used an existing CI image with the branch's sources 
mounted. A fresh local image build was blocked by a Python.org certificate 
trust error in the build container.
   
   ---
   
   ##### Was generative AI tooling used to co-author this PR?
   
   - [X] Yes — Codex (GPT-6)
   
   Generated-by: Codex (GPT-6) following [the 
guidelines](https://github.com/apache/airflow/blob/main/contributing-docs/05_pull_requests.rst#gen-ai-assisted-contributions)
   
   ---
   
   Drafted-by: Codex (GPT-6) (no human review before posting)
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to