Vamsi-klu opened a new pull request, #67053:
URL: https://github.com/apache/airflow/pull/67053

   Fix `BigQueryIntervalCheckTrigger` so triggerer re-instantiation preserves 
all explicit constructor arguments.
   
   The trigger forwarded `dataset_id`, `table_id`, and `poll_interval` to its 
parent constructor, but its overridden `serialize()` omitted them. After a 
triggerer round-trip those values could silently fall back to defaults. This 
change serializes the missing fields, removes the corresponding 
`check-trigger-serialize-init` allowlist entry, and adds regression coverage 
with a non-default polling interval plus an explicit serialize/reconstruct 
round-trip assertion.
   
   Related: #66961
   
   Tests:
   - `UV_CACHE_DIR=/tmp/uv-cache-bq-pr uv run ruff format 
providers/google/src/airflow/providers/google/cloud/triggers/bigquery.py 
providers/google/tests/unit/google/cloud/triggers/test_bigquery.py 
scripts/ci/prek/check_trigger_serialize_init.py`
   - `UV_CACHE_DIR=/tmp/uv-cache-bq-pr uv run ruff check --fix 
providers/google/src/airflow/providers/google/cloud/triggers/bigquery.py 
providers/google/tests/unit/google/cloud/triggers/test_bigquery.py 
scripts/ci/prek/check_trigger_serialize_init.py`
   - `prek run check-trigger-serialize-init --all-files`
   - `UV_CACHE_DIR=/tmp/uv-cache-bq-pr uv run --project providers/google pytest 
providers/google/tests/unit/google/cloud/triggers/test_bigquery.py -xvs`
   
   ---
   
   ##### Was generative AI tooling used to co-author this PR?
   
   - [X] Yes — Codex (GPT-5)
   
   Generated-by: Codex (GPT-5) following [the 
guidelines](https://github.com/apache/airflow/blob/main/contributing-docs/05_pull_requests.rst#gen-ai-assisted-contributions)
   
   ---
   Drafted-by: Codex (GPT-5) (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