DanielLeens commented on PR #11592: URL: https://github.com/apache/seatunnel/pull/11592#issuecomment-5167449181
Thanks for the update. I rechecked the current head on August 3, 2026. The CI fact I referenced in my previous review is now outdated: the `Build` check is no longer running/queued on this head. It is now ending in a cancelled state, and the contributor run behind that check currently shows `Run / kudu-connector-it (11, ubuntu-latest)` as the relevant cancelled lane: https://github.com/zhangshenghang/seatunnel/actions/runs/30432385889/job/90512890485 . That does not line up directly with this PR's current diff, which is limited to three `seatunnel-engine` files under the Zeta resource manager path. This branch is also behind `dev` (`behind_by=29`, compare status: `diverged`), and latest `dev` is already ahead with relevant upstream fixes such as `4c4b81859b09` (`[Fix][Connector-V2] Wait for Kudu client shutdown`) and `81d69d83bcc3` (`[CI][E2E] Stabilize hosted connector IT failures`). So for the CI side, the lowest-cost next step is to sync with the latest `dev` and rerun CI first. Separately, my previous source-side blocker is still open on this same head: the lifecycle contract around `refreshWorkerProfiles()` in `seatunnel-engine/seatunnel-engine-server/src/main/java/org/apache/seatunnel/engine/server/resourcemanager/AbstractResourceManager.java:283` still needs an explicit Javadoc/comment before merge. So at the moment this PR is blocked by both that source-side documentation item and the current upstream-sync / CI gate. -- 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]
