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

   Reverts #64723 (cherry-pick of #63826) from `v3-2-test` ahead of the 3.2.2 
release.
   
   ## Why
   
   #63826 was originally targeted for 3.3.0, not 3.2.x. The cherry-pick to 
`v3-2-test` was conservative — we want the lazy-import-providers optimization 
to bake longer on `main` before shipping in a patch release. Notably:
   
   - Large surface area (177 files: providers_manager rework, connection UI 
service refactor, provider.yaml schema addition, 80+ provider metadata files).
   - The change is a startup-performance optimization, not a bugfix — there's 
no user-visible incident driving its inclusion in 3.2.2.
   - It will continue to ship from `main` and is expected to land in 3.3.0 from 
the regular flow.
   
   ## What is preserved
   
   #65892 (cherry-pick of #63986, "Fix `TypeError` crashes on `/users/list` and 
`/roles/list` in FAB UI caused by concurrent API schema requests") **is 
independently valuable** and **is NOT being reverted**. Per the original PR 
description, the bug it fixes is in the pre-existing 
`_get_hooks_with_mocked_fab` global-`mock.patch` pattern, not in #63826's new 
APIs — confirmed by maintainer review. After this revert:
   
   - `connections.py` retains #65892's thread-safety guard (`if 
"wtforms.StringField" not in sys.modules:`) and real-WTForms `UnboundField` 
handling.
   - The standalone FAB UI concurrency fix continues to ship in 3.2.2.
   
   ## Conflict resolution
   
   Revert applied cleanly with no conflicts. `connections.py` auto-merged — 
#65892's improvements are preserved alongside the removal of the YAML-metadata 
code paths.
   
   ## Scope
   
   177 files changed, +27 / −365 — exact mirror of #64723's original diff.


-- 
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