Re: [I] Fix provider triggers whose serialize() drops __init__ parameters [airflow]

2026-05-17 Thread via GitHub


shahar1 closed issue #66961: Fix provider triggers whose serialize() drops 
__init__ parameters
URL: https://github.com/apache/airflow/issues/66961


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



Re: [I] Fix provider triggers whose serialize() drops __init__ parameters [airflow]

2026-05-15 Thread via GitHub


abhid-007 commented on issue #66961:
URL: https://github.com/apache/airflow/issues/66961#issuecomment-4459106288

   Quick correction to the comment above — the agent draft was posted without 
the attribution footer the repo asks for. Adding it here:
   
   ---
   Drafted-by: Claude Code (Opus 4.7); reviewed by @abhid-007 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]



Re: [I] Fix provider triggers whose serialize() drops __init__ parameters [airflow]

2026-05-15 Thread via GitHub


abhid-007 commented on issue #66961:
URL: https://github.com/apache/airflow/issues/66961#issuecomment-4459100698

   Picking up `BigQueryIntervalCheckTrigger` (the last of the five) — looks 
like @Nishieee has the other four covered in #66965 / #66966 / #66968 / and the 
Databricks Run trigger. Will keep the PR narrow to this single trigger and 
cross-reference #66960 so the `KNOWN_VIOLATIONS` entry can be removed from that 
side once both land.


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



Re: [I] Fix provider triggers whose serialize() drops __init__ parameters [airflow]

2026-05-14 Thread via GitHub


shahar1 commented on issue #66961:
URL: https://github.com/apache/airflow/issues/66961#issuecomment-4453736605

   > I’d love to work on this issue.
   > 
   > I’ll align each trigger’s serialize() return dict with its **init** 
parameters (adding any missing fields like caller / poll_interval / 
endpoint_prefix, storing values on self where needed) and add focused unit 
tests that round-trip serialize() --> **kwargs --> reinstantiation. Once the 
static check is clean, I’ll remove the corresponding entries from 
KNOWN_VIOLATIONS.
   
   Thank you, feel free to raise PRs.


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



Re: [I] Fix provider triggers whose serialize() drops __init__ parameters [airflow]

2026-05-14 Thread via GitHub


Nishieee commented on issue #66961:
URL: https://github.com/apache/airflow/issues/66961#issuecomment-4453577407

   I’d love to work on this issue.
   
   I’ll align each trigger’s serialize() return dict with its __init__ 
parameters (adding any missing fields like caller / poll_interval / 
endpoint_prefix, storing values on self where needed) and add focused unit 
tests that round-trip serialize() --> **kwargs --> reinstantiation. Once the 
static check is clean, I’ll remove the corresponding entries from 
KNOWN_VIOLATIONS.


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