Zixuan Liu

> @nodece Do you want to fix this flaky test? Okay

#16765 cannot fix this issue. Met this issue again: https://github.com/apache/pulsar/runs/7535091922?check_suite_focus=true#step:10:1253

Thread blocked: ``` "main" prio=0 tid=0x0 nid=0x0 waiting on condition java.lang.Thread.State: TIMED_WAITING on java.util.concurrent.CompletableFuture$Signaller@6d214cc3 at [email protected]/jdk.internal.misc.Unsafe.park(Native Method) at [email protected]/java.util.concurrent.locks.LockSupport.parkNanos(LockSupport.java:252) at [email protected]/java.util.concurrent.CompletableFuture$Signaller.block(CompletableFuture.java:1866) at [email protected]/java.util.concurrent.ForkJoinPool.unmanagedBlock(ForkJoinPool.java:3463) at [email protected]/java.util.concurrent.ForkJoinPool.managedBlock(ForkJoinPool.java:3434) at [email protected]/java.util.concurrent.CompletableFuture.timedGet(CompletableFuture.java:1939) at [email protected]/java.util.concurrent.CompletableFuture.get(CompletableFuture.java:2095) at...

@codelipenghui This is not easy to test for the function worker, a lot of mock tests are used here.

We can make an integration test to cover that but need to open the TLS port in the integration test.

> @nodece Any updates? Rebased, please help review. The test cannot be added temporarily.

> Please clean up the code. > > Also...do we have any test case about this feature? I remember we haven't tested for this, I'm working on adding integration tests...

ping @BewareMyPower, @RobertIndie

Link to https://github.com/apache/pulsar/pull/17393.

Hi @TakaHiR07, Thanks for your contribution! I think you should consider the compatibility here.