`ros2 launch` bug for `$OVERRIDE_LAUNCH_PROCESS_OUTPUT`
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:
- 20.04
- Installation type:
- Source
- Version or commit hash:
- Galactic and Humble
- DDS implementation:
- rmw_cyclonedds_cpp
- Client library:
- N/A
Steps to reproduce issue
export ROS_LOG_DIR=~/.ros2/reproduce/
export OVERRIDE_LAUNCH_PROCESS_OUTPUT=screen
ros2 launch your_package your_launch.xml # launch anything that logs
Expected behavior
The launch specific logging messages should only be output to the screen and should not be written to launch.log.
Actual behavior
Irrespective of $OVERRIDE_LAUNCH_PROCESS_OUTPUT's value, launch specific logs get written to $ROS_LOG_DIR/*/launch.log.
Additional information
Additionally, it would be good if users could disable launch specific logging entirely since this option is not provided at the moment.
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 by reproducing the issue with ros2 launch, ROS_LOG_DIR, and OVERRIDE_LAUNCH_PROCESS_OUTPUT=screen using a launch that logs. Trace how launch-specific messages are routed to launch.log; done means the override prevents those messages from being written there, with any separate disable-logging behavior decided explicitly.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- cli, tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100