Revision history [back]

It seems that plot_widget.py expects topic_type_str to be of type string, but it's of type str instead.

I'm not sure that's the problem: str is what string (if you're talking about the ROS2 idl type) is mapped to afaik.

The last line in the traceback shows this:

topic_type_str.find(']', start=array_idx + 1)

start is a "keyword argument" here. See this question on SO fi.

It seems that plot_widget.py expects topic_type_str to be of type string, but it's of type str instead.

I'm not sure that's the problem: str is what string (if you're talking about the ROS2 idl type) is mapped to afaik.afaik in Python clients.

The last line in the traceback shows this:

topic_type_str.find(']', start=array_idx + 1)

start is a "keyword argument" here. See this question on SO fi.

It seems that plot_widget.py expects topic_type_str to be of type string, but it's of type str instead.

I'm not sure that's the problem: str is what string (if you're talking about the ROS2 idl type) is mapped to afaik in Python clients.

The last line in the traceback shows this:

topic_type_str.find(']', start=array_idx + 1)

start is a "keyword argument" here. That is not supported. See this question on SO fi.

It seems that plot_widget.py expects topic_type_str to be of type string, but it's of type str instead.

I'm not sure that's the problem: str is what string (if you're talking about the ROS2 idl type) is mapped to afaik in Python clients.

The last line in the traceback shows this:

topic_type_str.find(']', start=array_idx + 1)

start is a "keyword argument" here. That is not supported. See this question on SO fi.

It seems to have been introduced in ros-visualization/rqt_plot#17 when rqt_plot was ported to ROS 2.

It looks like it's a copy-pasta or mistake (as it doesn't appear elsewhere in the file).