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

   Explicit `format_="dict"` and `format_="json"` currently fail because both 
Stackdriver list operators attempt to convert the hook's already-formatted 
output as protobuf objects. Preserve that output unchanged when `format_` is 
set, and retain protobuf-to-dictionary conversion when it is `None` for XCom 
serialization.
   
   Update both operator docstrings and add parametrized regression tests for 
both explicit formats. The existing default-format tests remain unchanged.
   
   Closes #73431.
   
   This targets the current Stackdriver implementation independently of the 
rename in #73354, as allowed in the issue.
   
   Validation passed in [Linux Breeze 
CI](https://github.com/ylv01/airflow/actions/runs/35580061477):
   
   - Regular and manual prek checks on both changed files, including provider 
type checks.
   - Complete Stackdriver operator and hook unit-test files.
   - Regression verification: reverting only the operator fix makes all four 
new cases fail.
   - Breeze selective checks.
   
   The unit tests and regression verification also passed in an [independent 
run](https://github.com/ylv01/airflow/actions/runs/35580894759). Local Ruff 
formatting/linting and `git diff --check` passed. Local Breeze testing was 
blocked by missing Docker on Windows, so the test and check suites ran on 
Linux. Verification workflows live only on separate fork branches and are not 
part of this PR.
   
   ---
   
   ##### Was generative AI tooling used to co-author this PR?
   
   - [X] Yes — OpenAI Codex (GPT-6)
   
   Generated-by: OpenAI Codex (GPT-6) following [the 
guidelines](https://github.com/apache/airflow/blob/main/contributing-docs/05_pull_requests.rst#gen-ai-assisted-contributions)
   


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