Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Make sure to initialize the rmw_message_sequence after init. (#175)
* Make sure to initialize the rmw_message_sequence after init. The documentation for "rmw_take_sequence" says: "Given `message_sequence` must be a valid message sequence, initialized by rmw_message_sequence_init() and populated with ROS messages whose type matches the message type support registered with the `subscription` on creation." As it stands, the take_sequence test fulfills the first part of that (it was initialized by rmw_message_sequence_init()), but doesn't fulfill the second part (populated by ROS messages). In certain situations, this could lead to an aborted test later on. Make sure to do the initialization to a known type before calling rmw_take_sequence. Signed-off-by: Chris Lalancette <[email protected]>
- Loading branch information