DanielLeens commented on PR #13008: URL: https://github.com/apache/seatunnel/pull/13008#issuecomment-6473760970
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-28T15:52:51+00:00), head `e86481f3500c37a627f6e2516b986a0ea40940b0`: [Build](https://github.com/apache/seatunnel/runs/122811202556) is `FAILURE`. The blocking jobs are [Run / Build SeaTunnel UI](https://github.com/DanielLeens/seatunnel/actions/runs/40641069202/job/122662801240) `cancelled`; [Run / engine-v2-it (11, ubuntu-latest)](https://github.com/DanielLeens/seatunnel/actions/runs/40641069202/job/122662801448) `failure`; [Run / engine-v2-it (17, ubuntu-latest)](https://github.com/DanielLeens/seatunnel/actions/runs/40641069202/job/122662801729) `failure`. The failed job list is observed, but its causal error is not established by the available summary. Please inspect the linked failed step/report before choosing a source change; no verified upstream sync-only cure is established in this follow-up. My [previous source conclusion](https://github.com/apache/seatunnel/pull/13008#pullrequestreview-5678861183) remains unchanged, including its independent source/documentation requests. 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 21 / behind 13, no merge conflict. Branch drift is metadata here and is not an additional sync request. -- 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]
