DanielLeens commented on PR #12173: URL: https://github.com/apache/seatunnel/pull/12173#issuecomment-5882006945
@Rangsh thanks for pinging @nzw921rx directly, and @SEZ9 thanks for the clear recap. Nothing has changed on my side since my last check on 2026-09-17: head is still `7948e2640`, F1–F6 remain closed, and my `APPROVED` from `5193337819` stands (the only PR-caused blocker at the time, the `spotless` violation, was verified fixed on this exact head, and the still-red jobs on that same Build run — `all-connectors-it`, `rocketmq`, `doris`, `paimon`, `engine-v2-it`, etc. — were outside this PR's diff, which only touches `seatunnel-benchmarks` and `JobHistoryService`). I just re-pulled the live PR state again rather than assuming it's unchanged: `reviewDecision` is still `CHANGES_REQUESTED` and `mergeStateStatus` is still `BLOCKED`, driven purely by @nzw921rx's 2026-09-10 review, which predates the `9a6077c58` docs fix that addressed its stated concern. Agreed with both of you that this is a stale review-state issue, not an open technical objection, and it needs a maintainer with write access (ideally @nzw921rx re-reviewing, or another committer) to clear it — that step is outside what my comment-only account can do here. @Rangsh, agreed on not pushing anything new to this branch unless needed — I'll re-confirm F1–F6 promptly on a new head if one becomes necessary, but for now there's nothing outstanding from the review side. -- 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]
