-
Notifications
You must be signed in to change notification settings - Fork 505
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
handling ros service call fail #55
Comments
Hi @OTL, would the status messages specified in the protocol meet your needs? |
May be no. You know that ROS service callback must return boolean value. rosbridge does nothing if the value is false, and does not send any responce to the client. status message seems to be different from this.From iPhone On 日, 9月 29, 2013 at 10:07 午前, Brandon Alexander <notifications@github.com="mailto:notifications@github.com">> wrote: Hi @OTL, would the status messages specified in the protocol meet your needs? — |
Yeah, I see what @OTL is getting at, it appears to be missing from the protocol entirely. |
Agreed. @OTL, would you be willing to submit a pull request with your suggested revision. Thanks for catching this! |
this might break my code for service providers connected via rosbridge, I will keep an eye on this topic.. |
I opened #56 . |
It is implemented to be just an extra field in the protocol so it shouldn't break anything (i.e., you can just ignore it) |
The pull request should have resolved this issue. |
rosbridge v2.0 protocol seems it does not support 'Failure of ros service'.
Failure means the service server returns false code.
I think it is better to handle the service result.
Adding
field to Service Response JSON will solve this problem.
(And if rosbridge server failed to call service, return JSON with this result:false for the response)
How do you think of this topic?
The text was updated successfully, but these errors were encountered: