DanielLeens commented on PR #11633: URL: https://github.com/apache/seatunnel/pull/11633#issuecomment-6397834930
Thanks for the contribution. A correction to my earlier upstream-fix guidance: [#12875](https://github.com/apache/seatunnel/pull/12875) is closed without merging. The actual fix is already merged into latest dev as [#12938](https://github.com/apache/seatunnel/pull/12938), commit `cc54bb433357b4cb45db9cd5d0743589c3111b79`. It corrects the JDBC option-completeness fixture as well as restoring the archived LLM wrapper's serialization UID. The unchanged head is `e0024e988f28227538f03a507b857597458866d4`, and [Build](https://github.com/apache/seatunnel/runs/118621283755) remains failed. The freshly retrieved [Java 11 Ubuntu UT log](https://github.com/li3zhi4/seatunnel/actions/runs/39203588198/job/118583520604) confirms `JdbcOptionRuleCompletenessTest.testSinkRuleDeclaresAllSinkOptions` rejects `numeric_special_value_as_null` in the sink fixture. This is the shared fixture mismatch addressed by #12938, not a new source finding for this PR. I checked that this head lacks that fix. Please **sync latest dev and rerun the failed unit jobs**, then confirm the PR's affected modules actually execute after the formerly failing reactor module. Do not keep waiting for #12875 or add the unrelated fixture option to product code here. The prior source-level conclusion remains clear; a successful current-head required Build and write-capable maintainer approval remain separate gates. Live comparison recorded in this batch: base dev, `diverged`, ahead 23 / behind 45. Daniel has READ permission; this is a technical follow-up, not an effective approval. No second source review is being issued on the unchanged head. -- 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]
