[humble] Fix for possible freeze in Recorder::stop() (backport #1381)#1388
[humble] Fix for possible freeze in Recorder::stop() (backport #1381)#1388MichaelOrlov merged 3 commits intohumblefrom
Conversation
a4fc984 to
4e3f109
Compare
|
According to the https://www.acodersjourney.com/20-abi-breaking-changes/
It seems that we have an ABI breaking changes in this PR and it shouldn't be merged. |
Yeah, it looks like it. The addition of member variables can change the layout of the underlying structure in memory, so it breaks ABI. |
4e3f109 to
ca05d24
Compare
|
@emersonknapp @clalancette I removed the newly added ABI/API compatibility reportAPI compatibility report between librosbag2_transport.so (X) and librosbag2_transport.so (Y) objects on x86_64Binary Test Info
Test Results
Problem Summary
Header Files 226__mbstate_t.h Source Files 7bag_rewrite.cpp Objects 1librosbag2_transport.so Test Info
Test Results
Problem Summary
Header Files 226__mbstate_t.h Source Files 7bag_rewrite.cpp Objects 1librosbag2_transport.so _Generated by ABI Compliance Checker 2.3 _ Currently, there are only changes in the header file in data types from
I did some research about
On all our supported platforms we have memory alignment by default and we are not using I think it will be safe to merge this PR. |
|
Pulls: #1388 |
|
New warnings on CI are unrelated to the changes in this PR and refer to the
cc: @fujitatomoya |
* Fix for possible freeze in Recorder::stop() - It was possible a freeze in recorder due to the race condition when calling Recorder::stop() while event publisher thread hasn't been fully started yet. Signed-off-by: Michael Orlov <michael.orlov@apex.ai> * Move event_publisher_thread_wake_cv_.notify_all() out of the mutex lock Signed-off-by: Michael Orlov <michael.orlov@apex.ai> --------- Signed-off-by: Michael Orlov <michael.orlov@apex.ai> (cherry picked from commit c6cc69a) # Conflicts: # rosbag2_transport/src/rosbag2_transport/recorder.cpp
Signed-off-by: Michael Orlov <michael.orlov@apex.ai>
Signed-off-by: Michael Orlov <michael.orlov@apex.ai>
ca05d24 to
4348b22
Compare
|
Re-run CI after rebase. |
This is an automatic backport of pull request #1381 done by Mergify.
Cherry-pick of c6cc69a has failed:
To fix up this pull request, you can check it out locally. See documentation: https://docs.github.com/en/github/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/checking-out-pull-requests-locally
Mergify commands and options
More conditions and actions can be found in the documentation.
You can also trigger Mergify actions by commenting on this pull request:
@Mergifyio refreshwill re-evaluate the rules@Mergifyio rebasewill rebase this PR on its base branch@Mergifyio updatewill merge the base branch into this PR@Mergifyio backport <destination>will backport this PR on<destination>branchAdditionally, on Mergify dashboard you can:
Finally, you can contact us on https://mergify.com