During integration testing of the rosbag2_processing_service it was found that some the service throws errors when trying to decode messages with the .idl definition in the schema.
Autoware auto messages are defined with this schema and currently need to be ignored in order to allow the service to continue operation.
Commit
Develop
Expected Behavior
All ros2 messages can be either decoded or ignored with a registered exception without stopping the processing for the entire rosbag
Actual Behavior
Trying to decode autoware_auto messages with the .idl schema causes the decode operation to error out, stopping the processing of the rosbag and returning an error to the processing status in the mysql database
Steps to Reproduce the Actual Behavior
Start the historical data processing with all the required services (rosbag2_processing_service, web-ui, mysql, influxdb)
Send a request to publish a rosbag with a topic that includes autoware_auto_msgs/msg/BoundingBoxArray type messages along with other message types.
Summary
During integration testing of the rosbag2_processing_service it was found that some the service throws errors when trying to decode messages with the .idl definition in the schema. Autoware auto messages are defined with this schema and currently need to be ignored in order to allow the service to continue operation.
Commit
Develop
Expected Behavior
All ros2 messages can be either decoded or ignored with a registered exception without stopping the processing for the entire rosbag
Actual Behavior
Trying to decode autoware_auto messages with the .idl schema causes the decode operation to error out, stopping the processing of the rosbag and returning an error to the processing status in the mysql database
Steps to Reproduce the Actual Behavior
Related Work
No response