Revision history [back]

I posted this to ros-users as well, but I'll add it here for completeness.

It appears that in Electric, rospy enforces that strings in ROS messages be ASCII strings, so the output of the python pickle module can't be encoded. to fix this we should be able to just change the "local_data" field in SmachContainerStatus from:

12 # A pickled user data structure
13 string local_data

to:

12 # A pickled user data structure
13 byte[] local_data

I don't currently have the time to test this fix, but I'm pretty sure this is the problem.

I posted this to ros-users as well, but I'll add it here for completeness.

It appears that in Electric, rospy enforces that strings in ROS messages be ASCII strings, so the output of the python pickle module can't be encoded. to To fix this we should be able to just change the "local_data" field in SmachContainerStatus from:

12 # A pickled user data structure
13 string local_data

to:

12 # A pickled user data structure
13 byte[] local_data

I don't currently have the time to test this fix, but I'm pretty sure this is the problem.

I posted this to ros-users as well, but I'll add it here for completeness.

It appears that in Electric, rospy enforces that strings in ROS messages be ASCII strings, so the output of the python pickle module can't be encoded. To fix this we should be able to just change the "local_data" field in SmachContainerStatus from:

12 # A pickled user data structure
13 string local_data

to:

12 # A pickled user data structure
13 byte[] uint8[] local_data

I don't currently have the time to test this fix, but I'm pretty sure this is the problem.