DanielLeens commented on PR #10643: URL: https://github.com/apache/seatunnel/pull/10643#issuecomment-6473958795
Thanks for the contribution. The CI fact cited in my previous conclusion has changed; this follow-up updates that gate on the unchanged reviewed head, without issuing another full source review. Gate snapshot (2026-10-28T16:00:36+00:00), head `1d50ab8212032104e46d4f2f4b465981526802b6`: [Build](https://github.com/apache/seatunnel/runs/122625517828) is `TIMED_OUT`. The blocking jobs are [Run / all-connectors-it-3 (17, ubuntu-latest)](https://github.com/chl-wxp/seatunnel-laowang/actions/runs/40630477103/job/122626515868) `cancelled`; [Run / all-connectors-it-3 (11, ubuntu-latest)](https://github.com/chl-wxp/seatunnel-laowang/actions/runs/40630477103/job/122626515908) `cancelled`. The returned jobs are cancelled; no product assertion failure is established by that state. Resume/rerun the cancelled required job through the existing workflow. There is no demonstrated upstream source fix for a cancelled execution, so a base sync alone is not a justified remedy. My [previous source conclusion](https://github.com/apache/seatunnel/pull/10643#pullrequestreview-5678873675) remains clear for the reviewed scope. CI is not being passed by inference, and this follow-up is not an effective approval. Comparison recorded in this scan: base `dev`, `diverged`, ahead 12 / behind 48, no merge conflict. Branch drift is metadata here and is not an additional sync request. My source blocker is cleared, but an older CHANGES_REQUESTED opinion may remain in the review summary after a COMMENT-only technical conclusion. With Daniel currently READ-only, a write-capable maintainer must separately reconcile the effective approval/dismissal gate; this clarification does not claim that action was performed. -- 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]
