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
i do not think so, this is default level so it just seems to work.
we can check that with arguments=['--ros-args', '--log-level', 'WARN'], this should not print any [INFO] messages.
as far as i can see from the source code, ComposableNodeContainer(Node).arguments are assigned to be user-defined arguments, not ros specific command line flags.
This may be due to components having their own configuration separate from that of the container (see here). ros2/rclcpp#978 is tracking that limitation, though I haven't got around to do what I said I was going to do then.
Bug report
Required Info:
Steps to reproduce issue
create a ComposableNode
Expected behavior
The log level is set to debug
Actual behavior
The log level doesn't change
Additional information
There are some topics related to this on answers.ros.org:
https://answers.ros.org/question/311471/selecting-log-level-in-ros2-launch-file/
https://answers.ros.org/question/370288/ros2-how-do-you-set-verbosity-of-a-composable-node/#370389
#383
Setting log level to at least info works fine, setting log level in source code also works:
Feature request
Allow setting Debug severity log.
The text was updated successfully, but these errors were encountered: