Caideyipi opened a new pull request, #19061: URL: https://github.com/apache/iotdb/pull/19061
## Description Independent `SHOW RECEIVERS` queries can collect different snapshots while receiver connections are being established or closed. During drop/stop cleanup, for example, the test wrapper can observe `ResultSet.next()` values of `[true, false, false]` and throw `InconsistentDataException`. Awaitility's `untilAsserted` does not retry this runtime exception by default. Retry `InconsistentDataException` in the pipe-absence, receiver-type, and protocol waits, matching the existing positive receiver check. Each poll executes a fresh query and closes its resources. Persistent inconsistencies and unmet assertions still fail through the existing timeout. ## Validation Previously completed checks reported for this diff: - Spotless passed. - Offline `clean verify` passed, with the required project modules rebuilt from clean source. - `testShowReceiversPipeIdsDisappearAfterDropPipe` and `testShowReceiversPipeIdsDisappearAfterStopPipe` passed on two clusters, each with 1 ConfigNode and 3 DataNodes: 2 tests, 0 failures, 0 errors. Independent source review found no actionable issues. Builds and ITs were not rerun during review or publication. The receiver-type and air-gap cases are not covered by the reported two-test result. This PR has: - [x] been self-reviewed. - [x] added comments explaining why the retry is needed. ##### Key changed classes - `IoTDBShowReceiversLifecycleIT` -- 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]
