feat: honor ADK_SUPPRESS_EXPERIMENTAL_FEATURE_WARNINGS#5124
feat: honor ADK_SUPPRESS_EXPERIMENTAL_FEATURE_WARNINGS#5124jinnigu wants to merge 1 commit intogoogle:mainfrom
Conversation
2d26241 to
8e97e24
Compare
|
Hi @jinnigu , Thank you for your contribution through this pull request! This PR has merge conflicts that require changes from your end. Could you please rebase your branch with the latest main branch to address these? Once this is complete, please let us know so we can proceed with the review. Can you also ensure the other failing tests are also fixed |
98cd4dd to
52127cf
Compare
Thanks @rohityan for helping review. The PR is now synced and reformatted. |
Please ensure you have read the contribution guide before creating a pull request.
Link to Issue or Description of Change
1. Link to an existing issue (if applicable):
2. Or, if no issue exists, describe the change:
Problem:
ADK_SUPPRESS_EXPERIMENTAL_FEATURE_WARNINGSdid not suppress all ADKexperimental warnings consistently. In practice, some experimental warnings
still appeared even when the env var was set, including the A2A flow described
in #5114.
Solution:
Make experimental warning suppression consistent across the affected ADK warning
paths.
experimental warnings.
Testing Plan
Unit Tests:
Coverage added / verified for:
Manual End-to-End (E2E) Tests:
Verified in a Python 3.11 environment that both A2A and registry-backed
experimental warnings are suppressed when
ADK_SUPPRESS_EXPERIMENTAL_FEATURE_WARNINGS=1is set, and that the A2A-specific env var still works independently.
Checklist
Additional context
compatibility.