Skip to content

Don't crash the action server if the client goes away. (backport #1114) #1218

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

Merged
merged 1 commit into from
Feb 11, 2024

Conversation

mergify[bot]
Copy link
Contributor

@mergify mergify bot commented Feb 9, 2024

This is an automatic backport of pull request #1114 done by Mergify.


Mergify commands and options

More conditions and actions can be found in the documentation.

You can also trigger Mergify actions by commenting on this pull request:

  • @Mergifyio refresh will re-evaluate the rules
  • @Mergifyio rebase will rebase this PR on its base branch
  • @Mergifyio update will merge the base branch into this PR
  • @Mergifyio backport <destination> will backport this PR on <destination> branch

Additionally, on Mergify dashboard you can:

  • look at your merge queues
  • generate the Mergify configuration with the config editor.

Finally, you can contact us on https://mergify.com

While doing some testing locally, I had a broken action
client that would send a goal, and then crash.  That
meant it wasn't available to receive the goal response,
nor the result response.  In this situation, my action
server was throwing an exception and crashing.

But that doesn't seem right.  The action server should continue
to run so other action clients can connect.  There are at
least 2 different ways we could accomplish this:

1. Document that the user needs to catch these exceptions
and deal with it themselves.
2. Handle these exceptions at the ActionServer layer.

There is some benefit to 1, in that the user has full control.
However, the problem is that the exceptions we throw in rclpy
aren't detailed enough for the user to disambiguate the errors.
So instead, we go for option 2 here.

Signed-off-by: Chris Lalancette <[email protected]>
(cherry picked from commit 091fe27)
@clalancette
Copy link
Contributor

clalancette commented Feb 9, 2024

CI:

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

@clalancette clalancette merged commit 64d22e4 into humble Feb 11, 2024
@delete-merged-branch delete-merged-branch bot deleted the mergify/bp/humble/pr-1114 branch February 11, 2024 13:26
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.

2 participants