RishabhBajaj97 commented on issue #74717: URL: https://github.com/apache/airflow/issues/74717#issuecomment-6167488832
I'd like to take a stab at the Go SDK side. Scoping to a focused first PR, I'd propose going with the "defensive exclude" path you hinted at in the issue body — add `execution_timeout` to the exclude list in `go-sdk/internal/genspec/authoring.go`, next to `is_setup`/`is_teardown`/etc. that are already excluded for the same "SDK cannot yet honour" reason. The field disappears from `TaskSpec`, so an author setting it gets a compile error instead of a task that silently ignores the timeout — matching the "worse than a missing field" principle already documented there. Properly implementing the runtime timer + `SetExecutionTimeout` dispatch is a larger structural change (the current `bundle.Task` interface exposes only `Execute()`, so there's no path for the task runner to read `ExecutionTimeout` at execution time without plumbing a new field through the task-handler map and the interface). Happy to do that as a follow-up PR once this defensive exclude lands, or to combine both if reviewers prefer. The TypeScript and Java pieces are also out of this first PR's scope — tracked separately. If a maintainer disagrees with the "exclude first, implement later" direction, say the word and I'll switch to the full runtime implementation. --- Drafted-by: Claude Code (Opus 4.7) (no human review before posting) -- 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]
