Re: [I] "execute cannot be called outside TaskInstance" warning fired despite being in a TaskInstance [airflow]

[via GitHub]

dabla commented on issue #41470:
URL: https://github.com/apache/airflow/issues/41470#issuecomment-2450121982

   > Hi @dabla, I'm using AWS MWAA 2.10.1 and I still get the same warning. 
Just wondering whether the issue is fixed in 2.10.1 or only in 2.9.3
   > 
   > Script,
   > 
   > ```
   > from airflow import DAG
   > from airflow.utils.dates import days_ago
   > from airflow.operators.bash import BashOperator
   > from airflow.utils.log.logging_mixin import LoggingMixin
   > 
   > class MyBashOperator(BashOperator, LoggingMixin):
   >     def execute(self, context):
   >         self.log.info("Executing MyBashOperator directly in the DAG 
definition")
   >         return super().execute(context)
   > 
   > dag = DAG(
   >     "test_bash_execution",
   >     default_args={
   >         "start_date": days_ago(1),
   >     },
   >     schedule_interval=None,
   > )
   > 
   > # Instantiate the operator
   > my_bash_task = MyBashOperator(
   >     task_id="my_bash_operator",
   >     bash_command="echo 'Testing direct execution'",
   >     dag=dag,
   > )
   > ```
   > 
   > Logs, <img alt="image" width="816" 
src="https://private-user-images.githubusercontent.com/182846498/381787558-a4fc4980-6751-4a85-97a1-e64fd0a4086c.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MzAzODczMzgsIm5iZiI6MTczMDM4NzAzOCwicGF0aCI6Ii8xODI4NDY0OTgvMzgxNzg3NTU4LWE0ZmM0OTgwLTY3NTEtNGE4NS05N2ExLWU2NGZkMGE0MDg2Yy5wbmc_WC1BbXotQWxnb3JpdGhtPUFXUzQtSE1BQy1TSEEyNTYmWC1BbXotQ3JlZGVudGlhbD1BS0lBVkNPRFlMU0E1M1BRSzRaQSUyRjIwMjQxMDMxJTJGdXMtZWFzdC0xJTJGczMlMkZhd3M0X3JlcXVlc3QmWC1BbXotRGF0ZT0yMDI0MTAzMVQxNTAzNThaJlgtQW16LUV4cGlyZXM9MzAwJlgtQW16LVNpZ25hdHVyZT03ZjQwNjJhNDRiNDIwMTBjMDVkZjBlNWI4Zjc1NThlYTMwNmYwZjRkNjk1MWRmOTQ1YTNlODI3NjhjNDQ3Nzg4JlgtQW16LVNpZ25lZEhlYWRlcnM9aG9zdCJ9._acIyB7ewJl_8Qjfgw8-_mMk0LDX5J5ISGisI7sFsTw";>
   
   The fix is not in Airflow 2.10.1 nor 2.10.2, I just checked the source code. 
I suppose it will be in 2.10.3 @potiuk @uranusjr ?


-- 
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: commits-unsubscr...@airflow.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org