sandeep-paluru commented on PR #75317: URL: https://github.com/apache/airflow/pull/75317#issuecomment-6322224487
Thanks, that makes sense. I read through #74869 and agree the runner-side math won't fit once the supervisor owns the deadline. Once it lands, I think the natural spot is `get_execution_timeout` on the server side: when the TI is resuming from deferral (`next_method` is set), send `execution_timeout - (now - start_date)` in `TIRunContext` instead of the full value, clamped at 0 so the existing "negative means already elapsed" handling fails it straight away. That way Python and language SDK tasks both get the right remaining time and the task runner doesn't need to know about deferral at all. I'll hold this one until #74869 merges and then rework it into that shape, with the tests moved to the execution API side. Happy to hear if a maintainer would rather see it go a different way. -- 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]
