SEPURI-SAI-KRISHNA commented on PR #11721: URL: https://github.com/apache/seatunnel/pull/11721#issuecomment-5331725137
CI is green at `7cfabc8`. All three checks on this head pass: | Check | Result | |---|---| | `Build` | SUCCESS | | `labeler` | SUCCESS | | `Notify test workflow` | SUCCESS | That confirms the diagnosis in my previous comment rather than just asserting it: the same shards went green on a rerun with **no code change**, so the earlier red was the `connector-clickhouse` Maven Central `Connection reset`, not this patch. @DanielLeens — that resolves your Issue 2. @davidzollo — one procedural thing is now the only blocker. Your `+1 if CI passes / LGTM` from `2026-08-16T10:39:06Z` was **auto-dismissed at `2026-08-18T04:45:27Z`**, 29 seconds after I pushed `7cfabc8c` (`Merge remote-tracking branch 'upstream/dev'`). That merge was needed because `dev` had independently touched `MultiTableSinkWriter.java` via the Dead Letter Queue work (#10306), and DanielLeens re-reviewed the merged result at that head. But the push tripped the repo's dismiss-stale-reviews rule, so the PR now reports `BLOCKED` even though every check is green. The condition you set has been met. Could you re-approve when you have a moment? Small correction to myself: on #11720 I described this PR as carrying a second approval from you. That is not accurate as of the dismissal above — DanielLeens's approval at `7cfabc8` is the only active one. Flagging it here rather than leaving the wrong version on the record. -- 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]
