Skip to content
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

Merged
merged 3 commits into from
Dec 21, 2020

Conversation

hidmic
Copy link
Contributor

@hidmic hidmic commented Dec 16, 2020

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 as bash interactive/non-interactive shells (see here).

@hidmic
Copy link
Contributor Author

hidmic commented Dec 16, 2020

I have not added regression tests yet. I plan to. At the very least, check the right events get sent.

Copy link
Member

@wjwwood wjwwood left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Makes sense.

@hidmic
Copy link
Contributor Author

hidmic commented Dec 21, 2020

CI up to launch, launch_ros, test_launch_ros, test_communication:

  • Linux Build Status
  • Linux-aarch64 Build Status
  • macOS Build Status
  • Windows Build Status

@hidmic
Copy link
Contributor Author

hidmic commented Dec 21, 2020

Thanks for the review guys!

@hidmic hidmic merged commit 55ca523 into master Dec 21, 2020
@delete-merged-branch delete-merged-branch bot deleted the hidmic/non-interactive-launch branch December 21, 2020 21:07
@hidmic
Copy link
Contributor Author

hidmic commented Mar 30, 2021

@jacobperron how do you feel about backporting this to Foxy?

@jacobperron
Copy link
Member

@jacobperron how do you feel about backporting this to Foxy?

Sounds okay to me 👍

@felixdivo
Copy link

Who would be responsible for that? Is there more involved then cherry-picking these three commits to a new branch targeted at branch foxy?

@jacobperron
Copy link
Member

Who would be responsible for that? Is there more involved then cherry-picking these three commits to a new branch targeted at branch foxy?

Anyone is welcome to propose a backport PR targeting the foxy branch (just as you've described; cherry-picking the relevant commits). If you do, feel free to mention me and/or hidmic.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants