DanielLeens commented on PR #10643: URL: https://github.com/apache/seatunnel/pull/10643#issuecomment-6503456643
Thanks @SEZ9. I confirm the same separation: my source blocker remains cleared, while the aggregate is timed out and the two all-connectors-it-3 jobs are cancelled. A cancelled execution is not a successful runtime result and does not prove a new port-selection bug. Rerun those existing cancelled jobs and share any actual failing step. Latest base provides no established source fix for a cancelled workflow, so a sync-only instruction is not warranted. A write-capable maintainer will separately reconcile any historical requested-change record after the gate is satisfied. Checked 2026-10-29T17:15:25+00:00; head `1d50ab8212032104e46d4f2f4b465981526802b6`. [Signal pull request update](https://github.com/apache/seatunnel/actions/runs/40630483881/job/122625443819) = `SUCCESS`; [Build](https://github.com/apache/seatunnel/runs/122625517828) = `TIMED_OUT` Comparison: base `dev`, head `1d50ab8212032104e46d4f2f4b465981526802b6`, `diverged`, ahead 12 / behind 60; 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]
