While writing the TCK for reactive sockets, my TCK code found the bug mentioned above.
val s4 = requestResponse("g", "h")
s4 cancel()
s4 assertCanceled()
s4 assertNoErrors()
s4 assertNotCompleted()
s4 assertReceivedCount 0
The line s4 cancel() causes the NPE on the client side, as it seems like the current implementation always expects request(n) to be called before cancel.
While writing the TCK for reactive sockets, my TCK code found the bug mentioned above.
The line
s4 cancel()causes the NPE on the client side, as it seems like the current implementation always expects request(n) to be called before cancel.