The GitHub Actions job "Tests" on airflow.git has succeeded. Run started by GitHub user uranusjr (triggered by uranusjr).
Head commit for run: 747a618f2c1d277989c723baebecd9b9318b3eae / Tzu-ping Chung <[email protected]> Add logging around listener Airflow does not currently have any logging for listeners, and only rely on individual listeners to log responsibly. This causes issues when a listener does not do it since it would have no trace at all in logs, and it is extremely difficult to find exactly what the offending component is (especially we would not even know a listener is at fault). This uses pluggy's hok monitoring feature to add logs when Airflow is calling a hook, and when a hook finishes executing. This should allow us to more easily identify when a hook emits an unhandled exception (it'd trigger the 'before' logging but not 'after'), and also provide some context what's passed into the hook for debugging. Ref: https://pluggy.readthedocs.io/en/stable/#call-monitoring I also referenced how Datasette does this: https://github.com/simonw/datasette/commit/232a30459babebece653795d136fb6516444ecf0 Report URL: https://github.com/apache/airflow/actions/runs/10916955270 With regards, GitHub Actions via GitBox --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
