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

Error with new service server and rosservice call #161

Closed
Carter12s opened this issue Jun 29, 2024 · 1 comment · Fixed by #170
Closed

Error with new service server and rosservice call #161

Carter12s opened this issue Jun 29, 2024 · 1 comment · Fixed by #170
Labels
bug Something isn't working ros1 For issues affecting the native ROS1 implementation

Comments

@Carter12s
Copy link
Collaborator

When trying to use rosservice call hit TAB to try to tab complete the message type.

You'll see

My guess is where not populating expected fields in the ConnectionHeader? But need to debug what is actually going on.

@Carter12s Carter12s added bug Something isn't working ros1 For issues affecting the native ROS1 implementation labels Jun 29, 2024
@Carter12s
Copy link
Collaborator Author

Okay above error was a red-herring. I had a borked networking setup with docker.

root@Moonboi:/# rosservice call /service_server_rs/my_set_bool
ERROR: Unable to determine type of service [/service_server_rs/my_set_bool].

^This is a real error. Likely because we aren't replying with type and md5sum as expected.
ROS documentation seems to contradict rospy behavior (go figure)

Wireshark of a rospy service response:
image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working ros1 For issues affecting the native ROS1 implementation
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant