-
Notifications
You must be signed in to change notification settings - Fork 265
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
Add the ability to record any key/value pair in 'custom' field in metadata.yaml #1038
Add the ability to record any key/value pair in 'custom' field in metadata.yaml #1038
Conversation
Gist: https://gist.githubusercontent.com/MichaelOrlov/f369c45f7fc66b7ec4d59dfa09eb0893/raw/e532c13f7dc3a8293cf61bfe23856d7524753c4a/ros2.repos |
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.
@allenh1 Thanks for your contribution and fixing issue with Windows build!
LGTM.
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.
@allenh1 Unfortunately CI build got failed, but now in another place.
SequentialWriterTest.split_event_calls_callback
Could you please try to figure out why it fails.
@gbiggs Could you please help with analysis in SequentialWriterTest.split_event_calls_callback
test failure, it was recently added by you.
88c48c0
to
ead8856
Compare
@MichaelOrlov Should be fixed now. |
Signed-off-by: Hunter L. Allen <hunter.allen@apex.ai>
Re-run CI: |
This pull request has been mentioned on ROS Discourse. There might be relevant details there: https://discourse.ros.org/t/ros-2-tsc-meeting-minutes-8-18-2022/27050/1 |
…adata.yaml (#1038) * Revert "Revert "Add the ability to record any key/value pair in the 'custom' field in metadata.yaml (#976)" (#984)" This reverts commit e7d4975. Signed-off-by: Hunter L. Allen <hunter.allen@apex.ai> * Ensure writer_ is destructed before intercepted_metadata_ Signed-off-by: Hunter L. Allen <hunter.allen@apex.ai>
This restores the changes from #976 that were reverted in #984.
Additionally, a fix was added to correct the destruction order in
SequentialCompressionWriterTest
.rosbag2/rosbag2_compression/test/rosbag2_compression/test_sequential_compression_writer.cpp
Lines 61 to 64 in e1f4349
The
write_metadata
call registered by the above hook is being invoked by the destructor forwriter_
. At this point, however, theintercepted_metadata_
object has already been destructed, leading to a segv.