Taragolis commented on issue #36948:
URL: https://github.com/apache/airflow/issues/36948#issuecomment-1909664795

   - https://github.com/apache/airflow/pull/36675 raise an error in Airflow 
versions where `logger_name` not implemented in  `LoggingMixin` class 
constructor yet
   
   Error which raised on Airflow 2.6.3
   
   ```console
   [2024-01-25, 08:29:34 UTC] Task failed with exception
   Traceback (most recent call last):
     File 
"/home/airflow/.local/lib/python3.10/site-packages/airflow/providers/slack/operators/slack.py",
 line 258, in execute
       self._method_resolver(
     File 
"/home/airflow/.local/lib/python3.10/site-packages/airflow/providers/slack/operators/slack.py",
 line 254, in _method_resolver
       return self.hook.send_file
     File "/usr/local/lib/python3.10/functools.py", line 981, in __get__
       val = self.func(instance)
     File 
"/home/airflow/.local/lib/python3.10/site-packages/airflow/providers/slack/operators/slack.py",
 line 82, in hook
       return SlackHook(
     File 
"/home/airflow/.local/lib/python3.10/site-packages/airflow/providers/slack/hooks/slack.py",
 line 117, in __init__
       super().__init__(logger_name=extra_client_args.pop("logger_name", None))
   TypeError: LoggingMixin.__init__() got an unexpected keyword argument 
'logger_name'
   ```
   
   I guess this affects only providers which explicitly propagate, something 
like `super().__init__(logger_name=kwargs.pop("logger_name", None))`:
   - [mongo: 
3.6.0rc1](https://pypi.org/project/apache-airflow-providers-mongo/3.6.0rc1)
   - [segment: 
3.5.0rc1](https://pypi.org/project/apache-airflow-providers-segment/3.5.0rc1)
   - [slack: 
8.6.0rc1](https://pypi.org/project/apache-airflow-providers-slack/8.6.0rc1)
   - [common.sql: 
1.11.0rc1](https://pypi.org/project/apache-airflow-providers-common-sql/1.11.0rc1)
   
   cc: @eladkal @hussein-awala 


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