-
Notifications
You must be signed in to change notification settings - Fork 793
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
Ref. 7288 Change removed when not on instance [7289] #961
Merged
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
IkerLuengo
force-pushed
the
bug/remove_keyed_not_found
branch
from
January 20, 2020 08:24
706641e
to
b9111b4
Compare
MiguelCompany
requested changes
Jan 20, 2020
return false; | ||
} | ||
else | ||
if (mp_subImpl->getAttributes().topic.getTopicKind() != NO_KEY) | ||
{ | ||
t_m_Inst_Caches::iterator vit; | ||
if (!find_key(change, &vit)) | ||
{ | ||
return false; |
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.
I think we should also remove the change when the key is not found
SubscriberHistory::remove_change_sub should remove from the general RTPS history even though it didn't find the change in the instance's history. Failing to do so will result on the same change returned once and again every time a new change is added to the subscriber's history
IkerLuengo
force-pushed
the
bug/remove_keyed_not_found
branch
from
January 22, 2020 11:48
7a14930
to
0102be9
Compare
MiguelCompany
approved these changes
Jan 22, 2020
Errors not related to changes |
IkerLuengo
added a commit
that referenced
this pull request
Feb 21, 2020
This is a port of #961 from 1.9.x
IkerLuengo
added a commit
that referenced
this pull request
Feb 24, 2020
This is a port of #961 from 1.9.x
MiguelCompany
pushed a commit
that referenced
this pull request
Feb 24, 2020
This is a port of #961 from 1.9.x
7 tasks
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.
SubscriberHistory::remove_change_sub should remove from
the general RTPS history even though it didn't find
the change in the instance's history.
Failing to do so will result on the same change returned
once and again every time a new change is added
to the subscriber's history