DanielLeens commented on PR #11897: URL: https://github.com/apache/seatunnel/pull/11897#issuecomment-5775011573
Thanks for the ping, @zhang-arvin. Head check: the rebase didn't produce a new commit here — `headRefOid` is still `d17b7a21023df5...`, the exact commit I already fully reviewed and approved on 2026-09-16. So there's nothing new in the diff to re-check; that approval still stands. CI update, now that it's settled: the Apache-side `Build` check completed with `FAILURE`, and this time the fork run itself (not a stale pointer) genuinely failed too. The two failing jobs are: - `paimon-connector-it (8, ubuntu-latest)` - `engine-v2-it (8, ubuntu-latest)` Neither touches anything in this PR's diff (still just the two design docs plus the `README.md` pointer, no `.java`/workflow files), so this isn't something introduced by your change. A plain rebase won't fix it since the content is identical to what already ran before — if you want a clean signal, retriggering/rerunning just those two failed jobs is a lower-cost next step than another push. If they fail again on rerun with the same content, that points to a pre-existing/environmental issue on `dev` rather than anything in this PR. One more thing worth flagging clearly: CI going green won't unblock this on its own. `mergeStateStatus` is still `BLOCKED` / `reviewDecision: REVIEW_REQUIRED` because @goutamadwant's 2026-08-20 `CHANGES_REQUESTED` review has never been formally cleared on GitHub, even though all three points it raised were fixed and re-verified independently across multiple rounds now. That needs a maintainer with write access to re-review and clear it (or dismiss the stale review) — it's outside what my review can resolve from here. -- 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]
