-
Notifications
You must be signed in to change notification settings - Fork 526
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
rosbridge stops spinning after a service is called #650
Comments
I believe there is a better way to implement the service call handler. Internally, the Service system seems to support async functions being used for the callback: https://github.com/ros2/rclpy/blob/38a408867719cb76c4b4f0b1caaf9cc191336970/rclpy/rclpy/executors.py#L369 Hopefully this will allow us to remove the |
@jtbandes I'm sorry to be late. Yes, it looks good to me and worked for my use case! |
@jtbandes hi, bro, I found a another issue when I use your branch, that is when I disconnect my client with rosbridge websocket server, then I reconnect my client to server, there will an error displayed "[rosbridge_websocket]: WebSocketClosedError: Tried to write to a closed websocket" any time when I call a service, so any solution to that??? Thanks so much. I just wondered the previous websocket connection is still be using with closed status. Is that right? |
@Stephenjerry that's interesting, sounds like something we could write a test for, would you be able to add the scenario you describe to |
I just solved it, my buddy, I deleted a line of code, then everything worked ok. A line of code that should be deleted is " self.protocol.external_service_list[service_name].service_handle.shutdown( |
I think this line of code doesn't make any sense, and it seems like blocking the reconnection pipline of same client, so that should be the matter. Do you think so? Or you can try it out like what I described above. Anyway, thank you so much, my bro |
**Public API Changes** None **Description** Fixes an issue reported by @Stephenjerry in #650 (comment). When a duplicate service is advertised by the client, the code now correctly shuts down the original service. There is still a `WebSocketClosedError` received with only a single client, when it advertises a service and then disconnects. Filed #684 to track this.
Description
Since rosbridge stops spinning, it can't receive the response here.
prewrite_message
function seems to be not running.Steps To Reproduce
Please see tier4#8.
Expected Behavior
Actual Behavior
The text was updated successfully, but these errors were encountered: