-
Notifications
You must be signed in to change notification settings - Fork 98
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
CommsBroker unregister being called? #270
Comments
Original comment by Steven Gray (Bitbucket: stgray).
|
Original comment by Alfredo Bencomo (Bitbucket: bencomo). I can also see the You should also try the |
Original comment by Steven Gray (Bitbucket: stgray). The error message about For example, I start with 2 robots, R1 and R2 and just have each robot send something to the other. This is great the first time, but the callbacks are never triggered again after restarting the comms nodes. Here’s the code I’m using for simple comms nodes - I did start with
|
Original comment by Alfredo Bencomo (Bitbucket: bencomo).
|
Original comment by Alfredo Bencomo (Bitbucket: bencomo). We will revisit this after Urban. |
Original comment by Nate Koenig (Bitbucket: Nathan Koenig). |
We have same problems - after restarting the comms client, it cannot bind to the same address and transmitting messages over subt comms doesn't work anymore. Maybe a hint - couldn't subscribing to multiple ports cause the problems (e.g., that only one port is unregistered when the client is destroyed)? I would also propose to re-label this as a major bug instead of minor proposal. |
Thank you for the suggestion. A bug is an issue that prevents the SubT Simulator from operating correctly or blocks development. Restarting robot code without restarting simulation is not a supported use case at this time. Therefore this issue is an enhancement. |
Solution proposed in #772. |
Original report (archived issue) by Steven Gray (Bitbucket: stgray).
This looks very much like
#33. I’m working on my comms node and would like to restart it multiple times without restarting the sim.To recreate - repeated running of the
subt_example_node
without also restarting the sim also results in this failure:Produced with the following – including killing and restarting
subt_example_node
once.
The text was updated successfully, but these errors were encountered: