DanielLeens commented on PR #13030: URL: https://github.com/apache/seatunnel/pull/13030#issuecomment-6473747268
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:20+00:00), head `7bd50c98251346b2635880b70953cc5483fef033`: [Build](https://github.com/apache/seatunnel/runs/122667155757) is `FAILURE`. The blocking jobs are [Run / engine-v2-it (17, ubuntu-latest)](https://github.com/DanielLeens/seatunnel/actions/runs/40641796047/job/122669220157) `failure`; [Run / jdbc-connectors-it-part-7 (11, ubuntu-latest)](https://github.com/DanielLeens/seatunnel/actions/runs/40641796047/job/122669220478) `failure`. Observed log evidence: `Failed to execute goal com.github.eirslett:frontend-maven-plugin:1.10.3:install-node-and-npm (install node and npm) on project seatunnel-engine-ui: Could not extract the Node archive: Could not extract archive: '/home/runner/.m2/repository/com/github/eirslett/node/16.13.2/node-16.13.2-linux-x64.tar.gz': EOFException -> [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/13030#pullrequestreview-5678790449) 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 1 / behind 7, 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]
