DanielLeens commented on PR #12922: URL: https://github.com/apache/seatunnel/pull/12922#issuecomment-6473783880
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:37+00:00), head `7d733de401716b2d9d68926504fe77c7a07a0f3f`: [Build](https://github.com/apache/seatunnel/runs/122812937798) is `FAILURE`. The blocking jobs are [Run / all-connectors-it-3 (17, ubuntu-latest)](https://github.com/fatmanverse/seatunnel/actions/runs/40664372182/job/122741470701) `failure`. Observed log evidence: `Failed to execute goal on project connector-bigquery-e2e: Could not resolve dependencies for project org.apache.seatunnel:connector-bigquery-e2e:jar:3.1.0-SNAPSHOT: Could not transfer artifact com.google.protobuf:protobuf-java-util:jar:3.25.8 from/to central (https://repo.maven.apache.org/maven2): GET request of: com/google/protobuf/protobuf-java-util/3.25.8/protobuf-java-util-3.25.8.jar from central failed: Connection reset -> [Help 1]` This evidence points to artifact transfer/extraction rather than establishing a product-diff defect. Rerun only the affected failed job after the transient artifact/cache problem is corrected. A simple base sync does not repair a connection reset or corrupted runner archive; I found no verified source-sync cure for that exact environment failure. My [previous source conclusion](https://github.com/apache/seatunnel/pull/12922#pullrequestreview-5681305565) remains clear for the reviewed scope. 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]
