linghengqian commented on issue #35052: URL: https://github.com/apache/shardingsphere/issues/35052#issuecomment-3140215194
> A third-party test at https://github.com/linghengqian/hive-server2-jdbc-driver/actions/runs/16550767465/job/46805233344?pr=37 shows that once any Linux Container is started on Windows Server 2025 through Rancher Desktop and testcontainers-java, the entire GraalVM Native Image will return an error code. - `GraalVM CE For JDK 24.0.2` does have an undocumented bug on the `Windows Server 2025`, and I had to use `Oracle GraalVM For JDK 25 EA` to fix the CI on `Windows Server 2025`. Of course, I'm referring to the bug where `testcontainers-java` doesn't work with the GraalVM Native Image compiled with `Windows Server 2025`. `Ubuntu 24.04` and `Windows 11 Home 24H2` don't have this problem. See https://github.com/linghengqian/hive-server2-jdbc-driver/pull/37 . - However, I have no intention of pushing similar operations to the master branch of shardingsphere before the release of `GraalVM CE For JDK 25`. Obviously, we have no way to pin the version of `Oracle GraalVM For JDK 25 EA` used in CI with a version number. https://github.com/graalvm/oracle-graalvm-ea-builds is constantly being updated.🤷♂️ - I personally don't have the convenience to test whether `Oracle GraalVM For JDK 25 EA` can fix the Netty DNS Resolver in my local environment, which is blocked by https://github.com/version-fox/vfox-java/issues/29. -- 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: notifications-unsubscr...@shardingsphere.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
