DanielLeens commented on PR #10962: URL: https://github.com/apache/seatunnel/pull/10962#issuecomment-6339533795
Thanks for your patience. The upstream status has changed since my preceding note: [#12938](https://github.com/apache/seatunnel/pull/12938) merged into `dev` at 2026-10-22 10:26 UTC (merge `cc54bb433357b4cb45db9cd5d0743589c3111b79`). I checked that current dev contains the merge and that its diff restores the historical `AbstractMultiCatalogTransform` serialization UID and makes the construction-only config transient. My earlier instruction to wait for that fix is now superseded. The archived-wrapper `LLMBooleanOutputTest.readsLegacyFactoryWrapperWithValidationDisabled` / `InvalidClassException` is the shared unit-test failure identified in the preceding review ([affected job](https://github.com/aakamara23/seatunnel/actions/runs/39392977060/job/118529742847)). This head is still `a17ee406e0fe28b83c33908370b171f1efaed9f7`; the current `dev` comparison is `diverged`, ahead 10 / behind 12. Please sync with the latest `dev` and rerun the affected unit checks first, plus any stage whose log showed the same archived-wrapper error. Keep unrelated transform-serialization patches out of this PR. This is a targeted remedy for that known upstream failure, not a claim that syncing fixes every failed stage. Other failed job families in the same head's run are `Dependency licenses`, `engine-v2-it`, `kudu-connector-it`. Their causes/results remain separate; this upstream patch does not establish that they pass. The existing source/documentation blockers in my preceding review remain open; the upstream CI correction clears none of those findings. Required CI and the final write-capable maintainer review remain gates. This is a CI-status follow-up only, with no new source findings or fresh full-review claim. -- 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]
