Add an option to disable creating log files by the launch system
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 155
- Forks
- 182
- Avg merge
- 2d 14h
- Merged PRs (30d)
- 6
Description
Feature request
Add an option to disable creating log files by the launch system.
Feature description
We deploy a ROS application which uses the launch subsystem using docker containers. We try to follow well known industry guidelines like Heroku's 12-factor app https://12factor.net/logs. This guideline states that the application should not force creating log files but instead it should output log entries using standard streams. This makes a lot of sense, especially if you deploy the application to an embedded device with a flash storage that wears quickly with unnecessary writes.
At the moment is seems that there is no way to disable creating launch.log file as it is created unconditionally in the get_logger function of the launch system: https://github.com/ros2/launch/blob/d9ffd805e3d9ca42fe4dd0019ae095e9eb0d4d72/launch/launch/logging/__init__.py#L350.
Implementation considerations
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 in launch/launch/logging/init.py at get_logger, where launch.log is created unconditionally. Trace how launch options reach this entry point and review the 12-factor requirement for standard-stream output. Done means an option prevents launch.log creation while preserving standard-stream logging, with regression coverage.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100