Owen-CH-Leung commented on PR #53529: URL: https://github.com/apache/airflow/pull/53529#issuecomment-3092398578
The bug only shows up when Airflow is started with `OpenSearchTaskHandler` and the `/config` endpoint is queried. That makes it an integration‑level concern, not a pure unit‑test case. From what I read, Airflow core purposely doesn’t want to import specific provider code (other than the common code obviously) at test time; the handler is pulled in dynamically at runtime based on config. The failure path involves the full request stack (TaskLogReader → ConfigResponse) plus the provider package. A unit test that stubs settings.remote_log_handler won’t tell us whether the real handler can be instantiated, its dependencies load, and the JSON flag is set end‑to‑end. Speaking more broadly - I think there's an integration test gap here. I couldn’t find any existing integration test that boots Airflow with each remote‑log provider and hits /config. Providers do have isolated unit tests, but nothing that covers the cross‑boundary behaviour we’re touching here -- 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]
