-
Notifications
You must be signed in to change notification settings - Fork 110
Shared subscriptions #675
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
Shared subscriptions #675
Conversation
Cleaned up code. Fixed index position bug. Fixed shared_subs_ adding algorithm.
Shared subscription publish deliver test is passed. |
Codecov Report
@@ Coverage Diff @@
## master #675 +/- ##
==========================================
- Coverage 82.69% 80.25% -2.44%
==========================================
Files 46 45 -1
Lines 7077 6945 -132
==========================================
- Hits 5852 5574 -278
- Misses 1225 1371 +146 |
shared subscriptions notation
QuestionIs
The important point is The publisher publishes |
Applied coding rules. Rename tags. For example, tag_combined used for multiple **combined** tags. I prefer to tag means a set of keys directly.
34de121
to
1f5d8db
Compare
I got https://github.com/redboltz/mqtt_cpp/pull/675/checks?check_run_id=1240841796#step:7:119 errors. It seems that s1 receives topic2 even if s1 only (shared) subscribes topic1. And s2 receives topic1 unexpected timing. At least former (s1 receives topic2) is wrong. I will debug it. |
I added logs. Now, test program take a severity level parameter. (default is warning) > ./shared_sub -- trace invalid round robin and invalid topic match are detected. NOTE: The message start with
|
I thin that |
I close the PR. It doesn't mean stop developing shared subscription support. After I updated it, then re-start developing shared subscription support. |
No description provided.