sortega opened a new issue, #54784:
URL: https://github.com/apache/airflow/issues/54784

   ### Apache Airflow version
   
   3.0.5
   
   ### If "Other Airflow 2 version" selected, which one?
   
   _No response_
   
   ### What happened?
   
   When you configure `logging_config_class` to have a custom `REMOTE_TASK_LOG` 
the value fails to be loaded for values like `module_name.LOGGING_CONFIG`.
   
   This is because in 
[logging_config.py:76](https://github.com/apache/airflow/blob/5523514dbd9326847a6a4c0dca930b8ab52e8bda/airflow-core/src/airflow/logging_config.py#L76)
 just the module_name is passed but `import_string` expect a path containing at 
least a dot.
   
   This bug was introduced with 
https://github.com/apache/airflow/commit/5523514dbd9326847a6a4c0dca930b8ab52e8bda#diff-86136b088eb194ccdcafb6cacddf923954f4dc89a36f608a85092be67f3904a5
   
   ### What you think should happen instead?
   
   It should work as in 3.0.4 and earlier versions.
   
   ### How to reproduce
   
   1. Add `logging_config_class = log_config.LOGGING_CONFIG` to your config file
   2. create `log_config.py` with `LOGGING_CONFIG` and `REMOTE_TASK_LOG` 
variables
   3. See how the remote task log fails to load in the logs
   
   ### Operating System
   
   Mac OS Sequoia 15.6
   
   ### Versions of Apache Airflow Providers
   
   It happens regardless of providers
   
   ### Deployment
   
   Virtualenv installation
   
   ### Deployment details
   
   Can be reproduced in airflow standalone mode
   
   ### Anything else?
   
   _No response_
   
   ### Are you willing to submit PR?
   
   - [x] Yes I am willing to submit a PR!
   
   ### Code of Conduct
   
   - [x] I agree to follow this project's [Code of 
Conduct](https://github.com/apache/airflow/blob/main/CODE_OF_CONDUCT.md)
   


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

Reply via email to