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

   ### Apache Airflow Provider(s)
   
   microsoft-azure
   
   ### Versions of Apache Airflow Providers
   
   apache-airflow-providers-microsoft-azure==12.6.1
   
   ### Apache Airflow version
   
   3.0.6
   
   ### Operating System
   
   Linux
   
   ### Deployment
   
   Astronomer
   
   ### Deployment details
   
   _No response_
   
   ### What happened
   
   Running the AzureDataFactoryRunPipelineOperator async + Airflow 3.0.3 gives 
this failure:
   ```
   ERROR - Task failed with exception: source="task"
   AirflowException: You cannot use AsyncToSync in the same thread as an async 
event loop - just await the async function directly.
   File 
"/usr/local/lib/python3.12/site-packages/airflow/sdk/execution_time/task_runner.py",
 line 920 in run
   File 
"/usr/local/lib/python3.12/site-packages/airflow/sdk/execution_time/task_runner.py",
 line 1215 in _execute_task
   File 
"/usr/local/lib/python3.12/site-packages/airflow/sdk/bases/operator.py", line 
1606 in resume_execution
   File 
"/usr/local/lib/python3.12/site-packages/airflow/providers/microsoft/azure/operators/data_factory.py",
 line 256 in execute_complete
   ```
   
   The operator runs fine on Airflow 2.
   
   ### What you think should happen instead
   
   The operator should not fail
   
   ### How to reproduce
   
   Run AzureDataFactoryRunPipelineOperator async + Airflow 3.0.3 or higher
   
   ### Anything else
   
   _No response_
   
   ### Are you willing to submit PR?
   
   - [ ] 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