DanielLeens commented on PR #11206: URL: https://github.com/apache/seatunnel/pull/11206#issuecomment-6503446040
The previously pending Build is now red. Multiple unit-test lanes fail at MultiTableSinkWriterTest.testRuntimeRegistrationFailurePolicy:234, and engine/MySQL CDC lanes are also unsuccessful. This PR changes runtime table registration, so that failure must not be dismissed as generic infrastructure noise or fixed through a speculative sync. The existing P0/P1 source findings in my full review (cross-worker barrier/monitor deadlock, runtime-table loss on automatic recovery, and include-filter registration contract) remain open. Correct those and the actual registration regression, then obtain exact-head CI; this is a gate correction, not a second list of source findings. Checked 2026-10-29T17:14:56+00:00; head `03973e5cbd3d7f215f80aa2e38e0fe9f053c00ab`. [Signal pull request update](https://github.com/apache/seatunnel/actions/runs/40642775355/job/122796019439) = `SUCCESS`; [Build](https://github.com/apache/seatunnel/runs/122809387163) = `FAILURE` Comparison: base `dev`, head `03973e5cbd3d7f215f80aa2e38e0fe9f053c00ab`, `diverged`, ahead 27 / behind 19; GitHub mergeable state `blocked`. Behind/diverged alone is recorded metadata and does not add a sync request. Daniel has READ repository permission. This is a discussion/CI clarification, not a new complete source review, an effective APPROVED event or dismissal of historical requested changes. A write-capable maintainer must perform any required final approval/dismissal. Thanks for keeping the follow-up focused. -- 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]
