[I] DAG import timeouts recorded in Airflow Database and displayed in Airflow UI [airflow]

[via GitHub]

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

   ### Description
   
   The following DAG:
   ```
   import datetime
   import time
   
   import airflow
   from airflow.operators.python import PythonOperator
   
   time.sleep(1000)
   
   with airflow.DAG(
       "import_timeout",
       start_date=datetime.datetime(2022, 1, 1),
       schedule=None) as dag:
   
     def f():
       print("Sleeping")
       time.sleep(120)
   
     for ind in range(10):
       PythonOperator(
           dag=dag,
           task_id=f"sleep_120_{ind}",
           python_callable=f,
       )
   ```
   
   is artificial example of DAG that will be timed out on import in DAG 
processor.
   
   In logs of Airflow we can see that there is AirflowTaskTimeout for that DAG:
   ![Screenshot 2024-09-03 13 21 
07](https://github.com/user-attachments/assets/6147a576-bfb8-4863-9f0c-9e788847f982)
   
   
   However, there is nothing exposed in Airflow UI that can give an idea of 
this.
   
   The idea is to record import timeouts information in Airflow database and 
display it in Airflow UI (similar to DAG import errors).
   Althought, it is not clear which model would be better to use, ImportError 
or DagWarning?
   
   
   ### Use case/motivation
   
   _No response_
   
   ### Related issues
   
   _No response_
   
   ### Are you willing to submit a 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: commits-unsubscr...@airflow.apache.org.apache.org

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