Silvio Giebl
Silvio Giebl
I am happy to explain in more detail and answer any questions to help move this forward. We are heavily affected by this bug because of failing/flaky tests.
I updated the branch on GitHub and now the workflows need approval again. I don't want to put pressure on you but it would be nice to get a rough...
If you have any questions or concerns I am happy to explain and discuss.
Related: #643
Hi @alexanderankin Thank you for your detailed description. > I think it makes sense to just use reactor You can already use reactor as the API, see here: https://hivemq.github.io/hivemq-mqtt-client/docs/installation/#optional-features >...
> deprecated RxJava2 The next version of the client will upgrade to RxJava 3 (and of course keep the already available reactor API). The next version will come once we...
> So with QoS 1 & 2, some special handling has to be done to guarantee that messages are correctly consumed. Special handling is actually not required. Instead just call...
Hi @climategadgets Although you are right that we should cover the most common unrecoverable problems in the default automatic reconnect, you can currently already do this manually, for example: ```java...
Current status: This feature was moved to version 1.3 as version 1.2 already contained a lot of features, so 1.2 could be released earlier. Nevertheless version 1.2 already contains some...