DanielLeens commented on PR #12920: URL: https://github.com/apache/seatunnel/pull/12920#issuecomment-6473787267
Thanks for the contribution. The merge-gate fact cited in my previous conclusion has changed: GitHub now reports a real merge conflict. This follow-up corrects that gate on the unchanged reviewed head; it is not another full source review or a sync request based only on being behind. Gate snapshot (2026-10-28T15:53:46+00:00), head `aceb3bad67515c6d4c5a3dce956fc81554db7cf7`: [Build](https://github.com/apache/seatunnel/runs/122812589591) is `FAILURE`. The blocking jobs are [Run / Code style](https://github.com/fatmanverse/seatunnel/actions/runs/40663873772/job/122733364563) `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/12920#pullrequestreview-5681294304) remains unchanged, including its independent source/documentation requests. CI is not being passed by inference, and this follow-up is not an effective approval. Separately, GitHub reports merge conflicts with `dev`. Please sync the latest base and resolve the conflicts first; the resulting new head needs checks and re-review. This conflict gate is independent of CI and existing source findings. -- 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]
