DanielLeens commented on PR #12904: URL: https://github.com/apache/seatunnel/pull/12904#issuecomment-6337984483
Thanks for the detailed location map, @wgzhao, and for the independent recheck, @SEZ9. There is no new head in this exchange, so my earlier source-level conclusion remains unchanged; I am not marking @SEZ9's independent threads resolved on their behalf. I also narrowed the current CI failures instead of repeating my earlier generic rerun advice: - [Code style / Check code specification](https://github.com/wgzhao/seatunnel/actions/runs/39608594369/job/119251186910) fails during `seatunnel-ci-tools` test compilation, in Lombok initialization: `NoSuchFieldException: com.sun.tools.javac.code.TypeTag :: UNKNOWN`. It is not a Spotless diff in your changed files. The job runs on `ubuntu-26.04` and the shared job has no explicit supported-JDK setup. - [changes / setup-python](https://github.com/wgzhao/seatunnel/actions/runs/39608594369/job/119251187307) fails because Python `3.11.0` x64 is unavailable for Ubuntu 26.04. Latest `dev` still uses `ubuntu-latest`, has no JDK setup in `code-style`, and pins Python `3.11.0` in `changes`; I found no merged correction for either gate. So **syncing current dev alone is not a fix, and a blind rerun is not a demonstrated remedy for these toolchain/image mismatches**. The minimal next step is a focused shared-CI correction by the workflow owners: select a project-supported JDK for the specification check and a compatible Python/runner combination. Once that lands, sync and rerun the affected jobs. Please keep unrelated Lombok/dependency changes out of this PR. The source review can stay focused on the endpoint/client changes; final merge still needs the actual required Build and @SEZ9's formal recheck. Thanks for making the review pointers easy to follow. -- 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]
