DanielLeens commented on PR #11206:
URL: https://github.com/apache/seatunnel/pull/11206#issuecomment-6514226425
Thanks @SEZ9. I checked the reported branch directly:
MultiTableSinkWriterTest.java:230-234 expects IOException only for FAIL_FAST;
line 234 is the other-policy branch, which calls applySchemaChange without
expecting an exception. Its injected writer factory at :224-226 throws
IOException("runtime registration unavailable"). CI reports the propagated
IOException at :234, so this is the runtime-registration failure-policy path,
not a generic runner-startup signal. Please preserve that failing case and
correct the policy/registration behavior rather than suppressing the test or
assuming an upstream sync resolves it. The P0 deadlock/recovery-table-loss and
include-filter contracts from the existing full review remain open
independently. The latest dev changes do not supply a registration-policy fix.
Earlier identifier/default/documentation items already reconciled in the full
review should not be reopened solely from an older discussion checklist.
Snapshot 2026-10-30T03:23:54.162575+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`.
Base `dev`; comparison `diverged`, ahead 27, behind 22; merge state
`blocked`. Behind/diverged alone is recorded metadata and does not add a sync
request. This is an unchanged-head discussion/CI clarification, not a new
complete source review, an effective approval or a dismissal of historical
requested changes.
--
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]
