The GitHub Actions job "Tests (AMD)" on airflow.git/backport-db6103c-v3-3-test has succeeded. Run started by GitHub user jason810496 (triggered by jason810496).
Head commit for run: 7db0cf4bbdd467d19858522d6066242050ca7747 / Jason(Zhe-You) Liu <[email protected]> [v3-3-test] Propagate resolved task log level to language SDK runtimes (#68712) * Propagate resolved task log level to language SDK runtimes A language-SDK runtime (Java, Go) launched by a coordinator cannot read Airflow's configuration, so it could only guess the task log level from inherited environment variables. The subprocess starts before the StartupDetails handshake arrives, so carrying the level in that message would reach it too late. Passing the supervisor-resolved level in the environment at launch makes it available before the runtime configures logging. * Propagate per-logger namespace levels to language SDK runtimes The root log level alone does not reflect a user's per-logger overrides (`[logging] namespace_levels`), so a runtime would still emit logs the worker is configured to suppress. Passing the levels alongside the root level keeps the runtime's filtering consistent with the rest of Airflow. Each language SDK reads and applies these on its own, so the contract is documented for SDK authors. * Remove logging metion in user-facing logs This should simply work, so we don't need to get into them. * Always set AIRFLOW__LOGGING__NAMESPACE_LEVELS Even when the configuration is empty, we can still set the environ without harm. This would actually be easier to handle in the runtime. --------- (cherry picked from commit db6103c) Co-authored-by: Jason(Zhe-You) Liu <[email protected]> Co-authored-by: Tzu-ping Chung <[email protected]> Report URL: https://github.com/apache/airflow/actions/runs/27933904618 With regards, GitHub Actions via GitBox --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
