linghengqian commented on issue #36672: URL: https://github.com/apache/shardingsphere/issues/36672#issuecomment-3642305386
I confirmed the simplest way to reproduce this bug through https://github.com/linghengqian/shardingsphere-switch-mode-test/commit/2432320f3c148bf29023493bb696ad73443af0dc . Simply include the graalvm tracing agent when executing the etcd integration unit test, and you can corrupt the ShardingSphere JDBC metadata, thereby corrupting the ZooKeeper integration unit test. ```xml <plugin> <groupId>org.graalvm.buildtools</groupId> <artifactId>native-maven-plugin</artifactId> <version>0.11.3</version> <extensions>true</extensions> <configuration> <agent> <enabled>true</enabled> </agent> </configuration> </plugin> ``` This is a bit beyond the scope of ShardingSphere's git. Let me see what's available in GraalVM's git. Alternatively, we need to update the jetcd-related dependencies used by ShardingSphere before testing. -- 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]
