reactive-streams

The window operators should indicate if the returned Flux for each window is safe to subscribe to multiple times.

Documentation Issue

I had a data processing pipeline that I introduced batching to, using the window operator. In this pipeline, it will retry a batch if it faces a transient error. When batching was added, and it retried, I saw a failure of `IllegalStateException: UnicastP

More details here
violetagg/reactor-netty-workshop#2

jUnit5 uses thread interrupt to stop hanging tests after the timeout expires. Some of our tests ignore InterruptedException by using:

• AwaitUtils
• netty’s syncUninterruptibly()
• awaitRequestNUninterruptibly
• awaitCancelledUninterruptibly

As the result, these tests may hang forever and jUnit5 won’t be able to stop them.
We should not ignore InterruptedException or run something uninte

Problem or use case

The client is currently only logging errors and warnings. For debugging purposes and during application development, it would be very useful to also have logs detailing the message flow.

Preferred solution or suggestions

TRACE level logging for incoming and outgoing MQTT control packet types, e.g., PUBLISH, SUBSCRIBE, PUBACK, SUBACK.

We make sure in the CI configuration to build with jdk8, but it would be safer to specify this in the build (javacOptions/scalacOptions) explicitly.