-
Notifications
You must be signed in to change notification settings - Fork 251
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 race condition in transport recorder #303
Fix race condition in transport recorder #303
Conversation
Signed-off-by: Carlos San Vicente <carlos.sanvicente@apex.ai>
Thanks for the contribution! Can you think of a way to add a regression test for this fix? Also, please a comment in the code for why this order of operations is necessary. |
Hi Emerson @emersonknapp, As regarding to explanation of why this order of operation is necessary: |
If it's too hard then that's ok, but I want to make sure we've always at least thought through regression tests for fixes, and it's good to note that thought process out in the open either way. Can you please add that comment to the code itself? That way the next implementer to change that is better informed. |
Sure, we will add comments about it in code. |
Signed-off-by: Michael Orlov <michael.orlov@apex.ai>
8aeb93d
to
4432d6b
Compare
Hi @emersonknapp Can you please kindly review/approve this changes. I've added comment about importance of order of operations. |
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.
Looks good! Thanks for pinging me again, I can lose updates sometimes
This PR fixes a race condition when creating a topic in robasg2 transport recorder.
Sometimes
test_rosbag2_record_end_to_end
fails by timeout with the following error messages:Signed-off-by: Carlos San Vicente carlos.sanvicente@apex.ai