New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support external ExecuteProcess output overrides. #218
Conversation
By means of an $OVERRIDE_LAUNCH_PROCESS_OUTPUT envvar. Signed-off-by: Michel Hidalgo <michel@ekumenlabs.com>
on all available options. | ||
:param: output configuration for process output logging. Defaults to 'log' | ||
i.e. log both stdout and stderr to launch main log file and stderr to | ||
the screen. Overridden externally by the $OVERRIDE_LAUNCH_PROCESS_OUTPUT |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nitpick: a new sentence should start on a newline. Same below.
Same comment about the $
as in ros2/launch_ros#10 (comment)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sure, I tend to add the $
to emphasize it's an envvar. FIxed.
Signed-off-by: Michel Hidalgo <michel@ekumenlabs.com>
In the future, please run CI on changes like this, even if they seem trivial. |
My bad! Did it fail on |
No, just try not to do so, in case it does. If it just touches comments, that's fine, if it touches only docs and you run tests locally that's ok too, but in a case like there where you touch Python code, definitely always run the CI, even if you think the code isn't covered by any tests. |
Fixes #214 by means of an
$OVERRIDE_LAUNCH_PROCESS_OUTPUT
envvar.Lacking a test to keep this PR simple, we can add one if necessary.