ChickenBenny commented on PR #75387: URL: https://github.com/apache/airflow/pull/75387#issuecomment-6497952954
Based on what we discussed offline: - `ti_run` now returns `execution_timeout` only for stub tasks, since that's the only place a runtime can get the value set on a Python `@task.stub`. - The value is sent as the task sets it: no value if the task doesn't set one, and `0` means no timeout (4a1ee6993b). - Python tasks work the same as last round: the runner sends its own value with `SetExecutionTimeout`. Getting the default from the worker instead will come in follow-up PRs (listed in the description). The stub stops storing the Dag processor's default, then the Go and TS SDKs fall back to the worker's default and send `SetExecutionTimeout` themselves. -- 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]
