Skip to content
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

Open
wants to merge 3 commits into
base: master
Choose a base branch
from

Conversation

marve
Copy link
Contributor

@marve marve commented May 2, 2024

… be delivered

@marve marve marked this pull request as ready for review May 2, 2024 21:56
@marve marve force-pushed the fix-at-least-once-delivery branch 2 times, most recently from 3989e91 to db29350 Compare May 3, 2024 21:42
@marve marve force-pushed the fix-at-least-once-delivery branch from a8d9fbd to 3365bf2 Compare May 8, 2024 21:04
var atLeastOnceSubscriptionResults = new List<CreateSubscriptionResult>();

IList<MqttApplicationMessage> retainedApplicationMessages = null;
if (subscribePacket.TopicFilters.Any(f => f.QualityOfServiceLevel != MqttQualityOfServiceLevel.AtLeastOnce))
Copy link
Collaborator

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?

Copy link
Contributor Author

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants