LucasEby opened a new issue, #24876: URL: https://github.com/apache/pulsar/issues/24876
### Search before reporting - [x] I searched in the [issues](https://github.com/apache/pulsar/issues) and found nothing similar. ### Read release policy - [x] I understand that [unsupported versions](https://pulsar.apache.org/contribute/release-policy/#supported-versions) don't get bug fixes. I will attempt to reproduce the issue on a supported version of Pulsar client and Pulsar broker. ### User environment Broker version: 4.2.0-SNAPSHOT Broker Operating system and hardware type: Linux x86_64 GNU/Linux Broker Java version: 17.0.16 ### Issue Description The below test performed 6 assertions with the ```expectThrows``` method which made a combination of 2 incorrect assumptions. It incorrectly assumed the order of the [HashMap](https://docs.oracle.com/javase/8/docs/api/java/util/HashMap.html) data despite HashMap not having a guaranteed order. Additionally, the test relied on [IOConfigUtils.java](https://github.com/apache/pulsar/blob/master/pulsar-io/common/src/main/java/org/apache/pulsar/io/common/IOConfigUtils.java) which utilizes a HashMap and iterates over the config fields with ```Field field : getAllFields(clazz)``` which utilizes the [getDeclaredFields](https://docs.oracle.com/javase/8/docs/api/java/lang/Class.html#getDeclaredFields--) method which returns an array of elements that are not sorted and are not in any particular order. As a result, the ordering can change due to different environments producing the contents in different orders despite the logical contents being the same. - pulsar-io/kafka/src/test/java/org/apache/pulsar/io/kafka/sink/KafkaAbstractSinkTest.java I discovered the problem with the [NonDex](https://github.com/TestingResearchIllinois/NonDex) tool. NonDex systematically detects incorrect tests that rely on non-deterministic behaviors in Java APIs—like assuming order of name/value pairs in json files — by exploring all specification-allowed outcomes. It does this by instrumenting undetermined APIs and randomizing the returned order/behavior within what the spec allows. Failures it exposes reliably indicate flawed assumptions in order that were never promised and should be fixed.So ### Error messages ```text [INFO] ------------------------------------------------------- [INFO] T E S T S [INFO] ------------------------------------------------------- [INFO] Running org.apache.pulsar.io.kafka.sink.KafkaAbstractSinkTest [ERROR] Tests run: 2, Failures: 1, Errors: 0, Skipped: 1, Time elapsed: 2.947 s <<< FAILURE! -- in org.apache.pulsar.io.kafka.sink.KafkaAbstractSinkTest [ERROR] org.apache.pulsar.io.kafka.sink.KafkaAbstractSinkTest.testInvalidConfigWillThrownException -- Time elapsed: 0.004 s <<< FAILURE! java.lang.AssertionError: expected [topic cannot be null] but found [acks cannot be null] at org.testng.Assert.fail(Assert.java:110) at org.testng.Assert.failNotEquals(Assert.java:1577) at org.testng.Assert.assertEqualsImpl(Assert.java:149) at org.testng.Assert.assertEquals(Assert.java:131) at org.testng.Assert.assertEquals(Assert.java:655) at org.testng.Assert.assertEquals(Assert.java:665) at org.apache.pulsar.io.kafka.sink.KafkaAbstractSinkTest.expectThrows(KafkaAbstractSinkTest.java:68) at org.apache.pulsar.io.kafka.sink.KafkaAbstractSinkTest.testInvalidConfigWillThrownException(KafkaAbstractSinkTest.java:202) at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:77) at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.base/java.lang.reflect.Method.invoke(Method.java:569) at org.testng.internal.invokers.MethodInvocationHelper.invokeMethod(MethodInvocationHelper.java:139) at org.testng.internal.invokers.InvokeMethodRunnable.runOne(InvokeMethodRunnable.java:47) at org.testng.internal.invokers.InvokeMethodRunnable.call(InvokeMethodRunnable.java:76) at org.testng.internal.invokers.InvokeMethodRunnable.call(InvokeMethodRunnable.java:11) at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264) at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136) at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635) at java.base/java.lang.Thread.run(Thread.java:840) [INFO] [INFO] Results: [INFO] [ERROR] Failures: [ERROR] org.apache.pulsar.io.kafka.sink.KafkaAbstractSinkTest.testInvalidConfigWillThrownException [INFO] Run 1: PASS [ERROR] Run 2: KafkaAbstractSinkTest.testInvalidConfigWillThrownException:202->expectThrows:68 expected [topic cannot be null] but found [acks cannot be null] [INFO] [INFO] [ERROR] Tests run: 1, Failures: 1, Errors: 0, Skipped: 0 ``` ### Reproducing the issue You can replicate the problem with the [NonDex](https://github.com/TestingResearchIllinois/NonDex) tool command: ``` mvn -pl pulsar-io/kafka -Dtest=org.apache.pulsar.io.kafka.sink.KafkaAbstractSinkTest#testInvalidConfigWillThrownException -DforkCount=1 -DnondexRuns=1 -DnondexSeed=974622 -DreuseForks=false edu.illinois:nondex-maven-plugin:2.2.1:nondex ``` ### Additional information _No response_ ### Are you willing to submit a PR? - [x] I'm willing to submit a PR! -- 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]
