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 the ROS1 bridge, the log messages get passed to ROS2 with different severity levels (1 instead of 10, 2 instead of 20, etc...). This causes a KeyError and an AssertionError in rqt_console/message_data_model.py:
I fixed it locally for me - should I create pull request? Otherwise, rqt_console is basically not usable with a ROS1 bridge. Probably there are also other failure cases, as the gaps between severity levels in ROS2 were probably on purpose to let space for custom levels.
Thanks!
Karl
PS: Where is rqt_console for Foxy maintained?
The text was updated successfully, but these errors were encountered:
Hi!
When using the ROS1 bridge, the log messages get passed to ROS2 with different severity levels (
1
instead of10
,2
instead of20
, etc...). This causes a KeyError and an AssertionError inrqt_console/message_data_model.py
:KeyError:
rqt_console/src/rqt_console/message_data_model.py
Line 89 in 6084e59
AssertionError:
rqt_console/src/rqt_console/message_data_model.py
Line 112 in 6084e59
I fixed it locally for me - should I create pull request? Otherwise,
rqt_console
is basically not usable with a ROS1 bridge. Probably there are also other failure cases, as the gaps between severity levels in ROS2 were probably on purpose to let space for custom levels.Thanks!
Karl
PS: Where is rqt_console for Foxy maintained?
The text was updated successfully, but these errors were encountered: