-
Notifications
You must be signed in to change notification settings - Fork 142
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 non-interactive launch.LaunchService runs #475
Conversation
Signed-off-by: Michel Hidalgo <[email protected]>
I have not added regression tests yet. I plan to. At the very least, check the right events get sent. |
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.
Makes sense.
Signed-off-by: Michel Hidalgo <[email protected]>
Signed-off-by: Michel Hidalgo <[email protected]>
Thanks for the review guys! |
@jacobperron how do you feel about backporting this to Foxy? |
Sounds okay to me 👍 |
Who would be responsible for that? Is there more involved then cherry-picking these three commits to a new branch targeted at branch |
Anyone is welcome to propose a backport PR targeting the |
Signed-off-by: Michel Hidalgo <[email protected]> Signed-off-by: Felix Divo <[email protected]> Co-authored-by: Michel Hidalgo <[email protected]>
Connected to #473. This patch allows the user to modify the underlying assumption
launch
currently makes about Ctrl+C behavior i.e. sent to all processes in the process group. In the same vein asbash
interactive/non-interactive shells (see here).