Setting log Debug level works only in code
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 155
- Forks
- 182
- Avg merge
- 2d 14h
- Merged PRs (30d)
- 6
Description
Bug report
Required Info:
- Operating System:
- Ubuntu 20.04...)
- Installation type:
- official foxy docker image
- Version or commit hash:
- DDS implementation: rmw_fastrtps_cpp
- Client library (if applicable):
Steps to reproduce issue
create a ComposableNode
import launch
from launch_ros.actions import ComposableNodeContainer, Node
from launch_ros.descriptions import ComposableNode
def generate_launch_description():
container = ComposableNodeContainer(
name="container",
namespace="",
package="rclcpp_components",
executable="component_container",
composable_node_descriptions=[
ComposableNode(
package="localization",
plugin="LocalizationNode",
name="localization"
)
],
arguments=['--ros-args', '--log-level', 'DEBUG']
)
return launch.LaunchDescription([container])
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
https://github.com/ros2/launch/issues/383
Setting log level to at least info works fine, setting log level in source code also works:
rcutils_ret_t rcutils_logging_set_logger_level (const char *name, int level);
Feature request
Allow setting Debug severity log.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the provided ComposableNodeContainer launch description and reproduce the behavior using its '--ros-args', '--log-level', 'DEBUG' arguments. Trace how that argument reaches the component container, then verify that the composable node emits debug-level logs when the change is complete.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100