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

connect() doesn't work if there's a delay #65

Open
Devin-botsync opened this issue Sep 5, 2020 · 2 comments
Open

connect() doesn't work if there's a delay #65

Devin-botsync opened this issue Sep 5, 2020 · 2 comments
Labels
bug Something isn't working

Comments

@Devin-botsync
Copy link

Devin-botsync commented Sep 5, 2020

connect() doesn't reconnect if there is some delay after closing the connection

Expected Result

ros.close()
// Connection is closed
// Wait for ~2 mins
ros.connect()
// Reconnected to websocket

Actual Result

ros.close()
// Connection is closed
// Wait for ~2 mins
ros.connect()
// Doesn't reconnect
ros.is_connected outputs False
waited for more that 5 mins for reconnection, didn't work

Reproduction Steps

import roslibpy
import time
ros = roslibpy.Ros(host, port)
ros.run()
ros.close()
time.sleep(120)
ros.connect()

System Information

Ubuntu 16.04, ROS kinetic, roslibpy v1.1.0.

I'm not sure if this is an expected behaviour.

@gonzalocasas gonzalocasas added the bug Something isn't working label Mar 29, 2021
@beverlylytle
Copy link
Member

Hi, sorry for the delayed response. In the last release (v1.2.1), a bug was fixed that I believe addresses this problem. Could you please confirm?

@xibei312
Copy link

@beverlylytle I had the same problem and I was sure the address was right

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

4 participants