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
create roslisp node, start node, run rxloggerlevel. Node should appear, but does not. Not sure whether this is a bug or a missing feature.
Conversation
Changed 18 months ago by bhaskara
type changed from defect to enhancement
This is a missing feature. Roslisp has a similar topic hierarchy to roscpp and a service interface for changing levels at runtime, and so I imagine it would be not too hard to add the specific interface that rxloggerlevel expects, but I haven't looked into this.
Changed 14 months ago by kruset
I created a patch for rospy doing that in #3749 (https://code.ros.org/trac/ros/ticket/3749). It is rather easy to do, just create 2 services returning a list of loggers and setting the level of one. The only problem is that the messages are currently defined in roscpp, so that would introduce a dependency to roscpp for the messages. Do you see any problem with that?
Changed 14 months ago by bhaskara
cc kwc, straszheim added
We should probably move the relevant ros messages into std_msgs and std_srvs, if that api is going to apply to multiple client libraries.
The text was updated successfully, but these errors were encountered:
Migrated from https://code.ros.org/trac/ros/ticket/3561
Reported by: kruset Owned by: bhaskara
Priority: major
Last modified ago: Nov 2011
create roslisp node, start node, run rxloggerlevel. Node should appear, but does not. Not sure whether this is a bug or a missing feature.
Conversation
Changed 18 months ago by bhaskara
This is a missing feature. Roslisp has a similar topic hierarchy to roscpp and a service interface for changing levels at runtime, and so I imagine it would be not too hard to add the specific interface that rxloggerlevel expects, but I haven't looked into this.
Changed 14 months ago by kruset
I created a patch for rospy doing that in #3749 (https://code.ros.org/trac/ros/ticket/3749). It is rather easy to do, just create 2 services returning a list of loggers and setting the level of one. The only problem is that the messages are currently defined in roscpp, so that would introduce a dependency to roscpp for the messages. Do you see any problem with that?
Changed 14 months ago by bhaskara
We should probably move the relevant ros messages into std_msgs and std_srvs, if that api is going to apply to multiple client libraries.
The text was updated successfully, but these errors were encountered: