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

Fix error message text about invalid servo parameters #2769

Merged
merged 1 commit into from
Mar 26, 2024

Conversation

nbbrooks
Copy link
Contributor

Description

Was debugging something and realized this error message is swapped.

I'll add this later when I'm on a dev computer, but looks like we should also add a check for if ((servo_params.command_out_type == "std_msgs/Float64MultiArray") && !servo_params.publish_joint_positions && !servo_params.publish_joint_velocities) - The previous check would not trigger that as it is specific to Float64 type.

Checklist

  • Required by CI: Code is auto formatted using clang-format
  • Extend the tutorials / documentation reference
  • Document API changes relevant to the user in the MIGRATION.md notes
  • Create tests, which fail without this PR reference
  • Include a screenshot if changing a GUI
  • While waiting for someone to review your request, please help review another open pull request to support the maintainers

@nbbrooks nbbrooks changed the title Fix error message text in servo.cpp Fix error message text about invalid servo parameters Mar 25, 2024
@sjahr sjahr added the backport-iron Mergify label that triggers a PR backport to Iron label Mar 26, 2024
@sjahr sjahr merged commit df78880 into moveit:main Mar 26, 2024
7 of 11 checks passed
mergify bot pushed a commit that referenced this pull request Mar 26, 2024
(cherry picked from commit df78880)

# Conflicts:
#	moveit_ros/moveit_servo/src/servo.cpp
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backport-iron Mergify label that triggers a PR backport to Iron
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants