-
Notifications
You must be signed in to change notification settings - Fork 202
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 #101, Always increment sequence counter #419
Conversation
9af4084
to
4e32599
Compare
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.
Could remove or mark CFE_SB_UNSUBSCRIPTION_RPT_EID as no longer generated.
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.
Remove CFE_SB_UNSUBSCRIPTION_RPT_EID (I think this was the CCB decision?)
will do |
dad1a39
to
5b94321
Compare
I believe I've properly squashed the branch, removed the unused EID, added unit tests...anything else? FYI for me what worked: % git checkout branch |
CCB 20200115 - Reviewed and approved for IC pending the changes already addressed above |
Adds logic and associated unit tests Removes no-longer-used EID
5b94321
to
54fbccb
Compare
Updated commit message (no code change) |
Describe the contribution
Note that this means route entries will never be removed and unsubscribe messages will never be sent.
Testing performed
Built and ran the SB unit tests. All passed, with changes included in this pull req.
Expected behavior changes
Sequence ID's of messages should increment even when there's (currently) no subscribers to that message ID.
System(s) tested on:
Debian VM
Contributor Info
Christopher.D.Knight@nasa.gov