You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When using rosbag record with splits and --repeat-latched, the latched messages in the subsequent bags are not marked as latched (and also lose the callerId).
This caused issue when I tried to replay a rosbag from the middle using -s.
Steps to reproduce
# Latched topic publisher, in the background
rostopic pub -l /foo std_msgs/Bool true &
# Non latched topic at 10Hz, so the bags are not empty, in the background
rostopic pub /bar std_msgs/Bool false -r 10 &
# Record at least 20 seconds
rosbag record /foo /bar -O foo.bag --split --duration 10 --repeat-latched
Kill the rosbag, the two publishers, and try to get /foo from the middle of foo_1.bag:
rostopic echo /foo # In another terminal
rosbag play foo_1.bag -s 5
Expected: the rostopic node displays data: True
Actual: nothing happen.
The text was updated successfully, but these errors were encountered:
Description
When using rosbag record with splits and
--repeat-latched
, the latched messages in the subsequent bags are not marked as latched (and also lose the callerId).This caused issue when I tried to replay a rosbag from the middle using
-s
.Steps to reproduce
Kill the rosbag, the two publishers, and try to get
/foo
from the middle of foo_1.bag:Expected: the rostopic node displays
data: True
Actual: nothing happen.
The text was updated successfully, but these errors were encountered: