DanielLeens commented on PR #12328: URL: https://github.com/apache/seatunnel/pull/12328#issuecomment-6473852291
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:56:07+00:00), head `2c565fac9fbd1d7a889bca1d13b52d22e7b43595`: [Build](https://github.com/apache/seatunnel/runs/121486621015) is `TIMED_OUT`. The blocking jobs are [Run / Dead links](https://github.com/albgen/seatunnel/actions/runs/40192601656/job/121166612962) `failure`; [Run / Build website](https://github.com/albgen/seatunnel/actions/runs/40192601656/job/121167188417) `cancelled`. The Dead links log identifies two HTTP 429 responses: the DeepWiki project URL and its remote badge URL in README. Build website was cancelled, so it is not evidence of a separate executed website compiler failure. Latest dev uses a local DeepWiki badge but still links the external project page; a sync alone is not a cure for that external rate limit. Please rerun only Dead links after the rate limit clears, keeping unrelated documentation/dependency changes out of this PR. The independent reviewer decision remains separate. My [previous source conclusion](https://github.com/apache/seatunnel/pull/12328#pullrequestreview-5643701675) 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 2 / behind 348, 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]
