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

   > [@dabla](https://github.com/dabla) I just checked the fix, but 
unfortunatly it does not seem to work.
   > 
   > ```
   > An error occurred: You cannot use AsyncToSync in the same thread as an 
async event loop - just await the async function directly.: 
source="airflow.providers.microsoft.azure.triggers.msgraph.MSGraphTrigger"
   > RuntimeError: You cannot use AsyncToSync in the same thread as an async 
event loop - just await the async function directly.
   > File 
"/home/airflow/.local/lib/python3.12/site-packages/airflow/providers/microsoft/azure/triggers/msgraph.py",
 line 196 in run
   > File 
"/home/airflow/.local/lib/python3.12/site-packages/airflow/providers/microsoft/azure/hooks/msgraph.py",
 line 437 in run
   > File 
"/home/airflow/.local/lib/python3.12/site-packages/airflow/providers/microsoft/azure/hooks/msgraph.py",
 line 455 in send_request
   > File 
"/home/airflow/.local/lib/python3.12/site-packages/airflow/providers/microsoft/azure/hooks/msgraph.py",
 line 354 in get_async_conn
   > File 
"/home/airflow/.local/lib/python3.12/site-packages/airflow/providers/microsoft/azure/hooks/msgraph.py",
 line 253 in _build_request_adapter
   > File 
"/home/airflow/.local/lib/python3.12/site-packages/airflow/sdk/definitions/connection.py",
 line 162 in extra_dejson
   > File 
"/home/airflow/.local/lib/python3.12/site-packages/airflow/sdk/execution_time/secrets_masker.py",
 line 134 in mask_secret
   > File 
"/home/airflow/.local/lib/python3.12/site-packages/airflow/jobs/triggerer_job_runner.py",
 line 740 in send
   > File "/home/airflow/.local/lib/python3.12/site-packages/asgiref/sync.py", 
line 186 in __call__
   > ```
   
   Indeed, I'm also encountering the same error in 3.0.6, it worked in 3.0.4 
and 3.0.5-rc2.


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