vatsrahul1001 opened a new pull request, #64625:
URL: https://github.com/apache/airflow/pull/64625
## Summary
Fix asset watcher triggers being deleted and recreated on every dag-parsing
loop.
`encode_trigger` wraps kwargs with `BaseSerialization.serialize()` (e.g.,
`tuple()` becomes
`{"__type": "tuple", "__var": []}`), which is correct for JSON-serializable
DAG definitions.
However, `add_asset_trigger_references` needs raw Python kwargs because
`Trigger._decrypt_kwargs`
returns native Python objects from the DB. This mismatch caused
`BaseEventTrigger.hash()` to
produce different hashes for the same logical trigger, resulting in an
infinite delete/recreate
cycle every parsing loop.
Replace `encode_trigger` with `_get_raw_trigger_kwargs` that unwraps any
BaseSerialization-encoded
values back to native Python objects, ensuring hash consistency between
DAG-defined and DB-stored
triggers. `encode_trigger` remains in use where it belongs — DAG
serialization for JSON storage.
- [X] Yes (please specify the tool below)
Claude
* Read the **[Pull Request
Guidelines](https://github.com/apache/airflow/blob/main/contributing-docs/05_pull_requests.rst#pull-request-guidelines)**
for more information. Note: commit author/co-author name and email in commits
become permanently public when merged.
* For fundamental code changes, an Airflow Improvement Proposal
([AIP](https://cwiki.apache.org/confluence/display/AIRFLOW/Airflow+Improvement+Proposals))
is needed.
* When adding dependency, check compliance with the [ASF 3rd Party License
Policy](https://www.apache.org/legal/resolved.html#category-x).
* For significant user-facing changes create newsfragment:
`{pr_number}.significant.rst`, in
[airflow-core/newsfragments](https://github.com/apache/airflow/tree/main/airflow-core/newsfragments).
You can add this file in a follow-up commit after the PR is created so you
know the PR number.
--
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]
