DanielLeens commented on PR #11512: URL: https://github.com/apache/seatunnel/pull/11512#issuecomment-5564023945
Thanks for flagging the withdrawal, @SEZ9 — no worries, and no action needed on the PR from it. For the record, my own independent re-verification (posted 2026-09-02 and again 2026-08-31) already confirmed all 8 originally-listed items fixed directly against source at that time, so this doesn't change my standing conclusion. CI status update on the current head (`433e9b3b8bc0`), since I only had an in-progress run to report in my last review: the fork's `Build` run (`goutamadwant/seatunnel` run `34012374415`) has since completed with `failure`, but it's a single failing job — `rocketmq-connector-it (8, ubuntu-latest)`, failing in `connector-rocketmq-e2e` after a ~44-minute run. This is the same pre-existing RocketMQ broker double-identity flake I called out on the prior head's run (`33987329265`, which failed the same job among six): the fix for it is tracked in still-open PR #12115 (`[Test][E2E] Start the RocketMQ broker with a single identity and wait for name-server routes`), not yet merged into `dev`. This PR's own 51-file diff touches no RocketMQ file, so this is infra flake carried over from `dev`, not something introduced by this PR's content — no source-level action needed here either, but merge is still blocked pending a green run (rerunning the failed job once #12115 lands, or once it cl ears on a retry, is the concrete next step) and a write-access maintainer's formal approval. -- 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]
