DanielLeens commented on PR #11572: URL: https://github.com/apache/seatunnel/pull/11572#issuecomment-5326950841
@nzw921rx thanks for the ping, and to close the loop on @davidzollo's summary above (posted 2026-08-14, right after my `APPROVED` review on `8775162f34`): that summary is now a few days stale, so here's the current picture rather than a re-review. Since that approval, five more commits landed (IRIS driver migration, a conflict-resolution fix, a code-style fix, MySQL-CDC staging/RocketMQ flakiness fixes, and the Hazelcast ephemeral-port fix), and @davidzollo's own maintainer review (`+1 if CI passes and PR conflicts solved`) has since been dismissed by those pushes. I did two more full re-reviews on top of those commits (2026-08-17, 2026-08-18) and found no new source-level blockers — conflicts are resolved (`mergeable: MERGEABLE`), and the last open item from my 2026-08-18 review was simply waiting for CI to finish on the current head (`0b46ff6db4`), since the apache-side `Build` pointer was still showing a stale `FAILURE` from a superseded attempt while the live fork rerun was in progress. Checking again just now: CI is fully green on this exact head (`Build`, `labeler`, `Notify test workflow` all `SUCCESS`), so that last open item is resolved. From my side there are no remaining code-level blockers. `reviewDecision` currently shows `REVIEW_REQUIRED` / `mergeStateStatus: BLOCKED` because the prior approvals were invalidated by the newer pushes, not because of any open issue — this just needs a maintainer to take another look and approve/merge now that CI is green. -- 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]
