Fix "messageExpiryInterval" check failure in MQTT 5 publish #19
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…eping its default value
|
Good work, thanks! I'll add a small regression test and then release this. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Mqtt5PublishBuilderwill checkmessageExpiryIntervalparameter in its builder method, which results in assertion failure ifPublishingOptions.messageExpiryIntervalis left unspecified or maintained at its default setting.Using
Mqtt5PublishBuilder#noMessageExpiry()to explicitly denote "no message expiry" when retaining the defaultmessageExpiryInterval.This fixes #18.
The upstream have introduced a special value
-1to disable message expiry inMqtt5PublishBuilder.messageExpiryInterval, but haven't released so far.References: hivemq/hivemq-mqtt-client#580, hivemq/hivemq-mqtt-client#604.