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

   In general we accept bugs which could be reproduce in Open Source 
implementation on latest stable version of Airflow, for that purpose you could 
try to use provided Docker Compose from [Running Airflow in Docker  
](https://airflow.apache.org/docs/apache-airflow/stable/howto/docker-compose/index.html#running-airflow-in-docker)
   
   There are several reasons for this
   - Community lack of knowledge of deployments Managed services
   - What kind of changes made by owners of Managed Airflow
   - And there is at least 7 different companies provide Airflow as a Service. 
[Ecosystem: Airflow as a 
Service](https://airflow.apache.org/ecosystem/#airflow-as-a-service)
   
   A bit more information about `execution_timeout` itself, it is implemented 
by use 
[SIGALARM](https://www.gnu.org/software/libc/manual/html_node/Alarm-Signals.html)
 signal, and behaviour of this signal might not work in some cases, 
   
   This block of code could demonstrate it demonstrate
   
   ```python
   import signal
   import time
   
   
   class TimeoutError(Exception):
       ...
   
   
   def some_func():
       try:
           while True:
               time.sleep(0.1)
       except Exception:
           pass
       print("Nope")
   
   
   def some_another_func():
       while True:
           time.sleep(0.1)
       print("Nope")
   
   
   def handler(signum, frame):
       raise TimeoutError(f"Timeout!")
   
   
   TIMEOUT = 2
   
   ### This one not failed, because error will caught in try..except, and 
instead of TimeoutError ``Nope`` would print
   signal.signal(signal.SIGALRM, handler)
   signal.alarm(TIMEOUT)
   try:
       some_func()
   finally:
       signal.alarm(0)
   
   ### This one failed, and TimeoutError will raise
   signal.signal(signal.SIGALRM, handler)
   signal.alarm(TIMEOUT)
   try:
       some_another_func()
   finally:
       signal.alarm(0)```
   


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