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

For the Joint Trajectory action server, standardize returned error results. #375

Closed
adamdbrw opened this issue Jun 29, 2023 · 1 comment
Closed
Labels
feature/robotics This item is related to robotics. good-first-issue Issue ready for a new contributor according to the help wanted guidelines. kind/enhancement Enhancement to an existing feature. priority/minor Lowest priority. Work that may be scheduled

Comments

@adamdbrw
Copy link
Contributor

Currently, some ways of returning errors are not fully informative for the action client.

  • Review the specification of action servers and control_msgs::action::FollowJointTrajectory.
  • Correct the flow of results such as from cancellation or invalid goal.
    For example, if the goal cannot be reached, first accept it, and then return a failure result. Currently it is rejected with rclcpp_action::GoalResponse::REJECT, which does not leave an information as to why.
@adamdbrw adamdbrw added kind/enhancement Enhancement to an existing feature. good-first-issue Issue ready for a new contributor according to the help wanted guidelines. priority/minor Lowest priority. Work that may be scheduled feature/robotics This item is related to robotics. labels Jun 29, 2023
@michalpelka
Copy link
Contributor

Fixed with 386 by @lewandowskikacper .

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature/robotics This item is related to robotics. good-first-issue Issue ready for a new contributor according to the help wanted guidelines. kind/enhancement Enhancement to an existing feature. priority/minor Lowest priority. Work that may be scheduled
Projects
None yet
Development

No branches or pull requests

2 participants