DanielLeens commented on PR #11602: URL: https://github.com/apache/seatunnel/pull/11602#issuecomment-6503431980
Thanks @SEZ9; that matches my current source conclusion. The per-job JobMaster documentation correction remains open: the bound is per worker rather than one overall deadline. The unchanged head does not resolve that request. The separate current Build discovery/action gate still needs an exact-head fork workflow run; enable workflows only if the fork actually shows them disabled, otherwise start/link the existing Build. No unrelated source or dependency change is requested merely to activate CI. Checked 2026-10-29T17:14:19+00:00; head `e25b3354e65afa6dec118820cb187f87f24a2a72`. [Signal pull request update](https://github.com/apache/seatunnel/actions/runs/40168025208/job/121480713925) = `SUCCESS`; [Build](https://github.com/apache/seatunnel/runs/121486172860) = `ACTION_REQUIRED` Comparison: base `dev`, head `e25b3354e65afa6dec118820cb187f87f24a2a72`, `diverged`, ahead 20 / behind 58; GitHub mergeable state `blocked`. Behind/diverged alone is recorded metadata and does not add a sync request. Daniel has READ repository permission. This is a discussion/CI clarification, not a new complete source review, an effective APPROVED event or dismissal of historical requested changes. A write-capable maintainer must perform any required final approval/dismissal. Thanks for keeping the follow-up focused. -- 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]
