-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix(server): at-least-once messages received during subscription must… #1988
base: master
Are you sure you want to change the base?
Conversation
3989e91
to
db29350
Compare
a8d9fbd
to
3365bf2
Compare
var atLeastOnceSubscriptionResults = new List<CreateSubscriptionResult>(); | ||
|
||
IList<MqttApplicationMessage> retainedApplicationMessages = null; | ||
if (subscribePacket.TopicFilters.Any(f => f.QualityOfServiceLevel != MqttQualityOfServiceLevel.AtLeastOnce)) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why is this only relevant for at least once QoS? Isn't this also beneficial for QoS 0 and 2?
Or are you fixing a specific issue in your project here?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good question. The project wherein we discovered this bug uses solely AtLeastOnce
. But I think you're right that it may fix potential issues with AtMostOnce
and ExactlyOnce
as well.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@chkr1011 Is this PR sufficient as-is or are you requesting that I make changes?
… be delivered