-
Notifications
You must be signed in to change notification settings - Fork 778
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
[20706] Make reader get_first_untaken_info() coherent with read()/take() (backport #4696) #4708
Conversation
* Refs #20706: Add regression BB test Signed-off-by: Mario Dominguez <[email protected]> * Refs #20706: Fix Signed-off-by: Mario Dominguez <[email protected]> * Refs #20706: Apply review suggestions Signed-off-by: Mario Dominguez <[email protected]> --------- Signed-off-by: Mario Dominguez <[email protected]> (cherry picked from commit 5fbd88e)
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.
as feedback, we originally found this problem with humble
, and then confirmed with rolling
as well. we have confirmed that this PR resolves the problem with humble
as well based on 2.6.x
branch.
@richiprosima please test this |
The new test failed here. Could you take a look @Mario-DL ? |
Signed-off-by: Mario Dominguez <[email protected]>
@richiprosima please test this |
Despite the patch fixes the issue it is weird that HelloWorld type declaration has a std::string instead of a fixed string as the idl states. Will double check that. |
Description
This PR corrects the behavior of
get_first_untaken_info()
so that it retrieves the first valid cache change (checking whether the change is in the future or not), instead of just returning the first one in the instance (sorted by sourcetimestamp).In the scenario of having multiple reliable writers and one reader with history size > 1 in the same topic, it can happen that
get_first_untaken_info()
returnsOK
(as it is not currently checking whether the change is in the future) buttake()
returnsNO_DATA
because the change is in the future.In addition, a brief doxygen documentation is added to be aware that the method is meant to be followed by a
read()
ortake()
since it does not modify the status condition of the entity.@Mergifyio backport 2.13.x 2.10.x 2.6.x
Fixes ros2/rmw_fastrtps#749
Contributor Checklist
Commit messages follow the project guidelines.
The code follows the style guidelines of this project.
Tests that thoroughly check the new feature have been added/Regression tests checking the bug and its fix have been added; the added tests pass locally
Any new/modified methods have been properly documented using Doxygen.
Any new configuration API has an equivalent XML API (with the corresponding XSD extension)
Changes are ABI compatible.
Changes are API compatible.
N/A New feature has been added to the
versions.md
file (if applicable).N/A New feature has been documented/Current behavior is correctly described in the documentation.
Applicable backports have been included in the description.
Reviewer Checklist
This is an automatic backport of pull request #4696 done by [Mergify](https://mergify.com).