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

Local subscriptions causing it to blow up #92

Open
stonier opened this issue Oct 20, 2016 · 4 comments
Open

Local subscriptions causing it to blow up #92

stonier opened this issue Oct 20, 2016 · 4 comments

Comments

@stonier
Copy link
Collaborator

stonier commented Oct 20, 2016

To reproduce (100%):

  • Run gopher rocon on podium
  • Open a podium konsole
  • Run rostopic echo /sentience/reality
  • CTRL-C the rostopic echo

Over in the main window:

received. 0 bytes were received. Please check sender for additional details.
[INFO] [WallTime: 1476941171.550023] /rostful Pyros.rosinterface : Deleting rosinterface topic /sentience/reality Reality
[WARN] [WallTime: 1476941171.550878] Could not process inbound connection: Internal error processing topic [/sentience/reality]{'message_definition': "##########################################################################################\n#\n# For exposing the robot's perception of itself and the world.\n#\n##########################################################################################\n\n##############################\n# Status Indicators\n##############################\n\nuint8 STATUS_IDLE                             = 0\nuint8 STATUS_BUSY_PARKING                     = 1\nuint8 STATUS_BUSY_UNPARKING                   = 2\nuint8 STATUS_BUSY_DOCKING                     = 3\nuint8 STATUS_BUSY_UNDOCKING                   = 4\nuint8 STATUS_BUSY_TRAVELLING                  = 5\nuint8 STATUS_BUSY_WILL_DEPART                 = 8\nuint8 STATUS_BUSY_CANCELLING                  = 9\nuint8 STATUS_BUSY_OTHER                       = 10\nuint8 STATUS_WAITING_FOR_AUTHENTICATION       = 50\nuint8 STATUS_WAITING_FOR_INPUT                = 51\nuint8 STATUS_PAUSED_EMERGENCY                 = 100\nuint8 STATUS_BROKEN_OTHER                     = 200\n\n##############################\n# Status Messages\n##############################\n\nstring STATUS_IDLE_MSG                        = bored, waiting for something to do\nstring STATUS_BUSY_PARKING_MSG                = finding a place to park/dock\nstring STATUS_BUSY_UNPARKING_MSG              = unparking/undocking\nstring STATUS_BUSY_TRAVELLING_MSG             = travelling between locations\nstring STATUS_WAITING_FOR_AUTHENTICATION_MSG  = waiting for a hooman to authenticate\nstring STATUS_WAITING_FOR_INPUT_MSG           = yawn, waiting for input\nstring STATUS_BUSY_WILL_DEPART_MSG            = received a new job and preparing to move out\nstring STATUS_BUSY_CANCELLING_MSG             = current job cancelled so heading home\nstring STATUS_BUSY_OTHER_MSG                  = engaged in some nefarious activity and do not wish to share\nstring STATUS_PAUSED_EMERGENCY_MSG            = a rogue human has activated the emergency button\nstring STATUS_BROKEN_OTHER_MSG                = broken, urgently needing help from a hooman\n\n##############################\n# Other Flags\n##############################\n\nint8 CONCERT_NEVER_CONNECTED=-1\n\n##############################\n# Other Messages\n##############################\n\nstring MESSAGE_BABBLE=Is babbling incoherently, you're going to need a babelfish\nstring MESSAGE_FEELINGS=Feelings are dumb, and should be hated\nstring MESSAGE_SAD=I dont have emotio
...
...

And rostful now no longer exposes that topic.

@asmodehn
Copy link
Member

This should be fixed by pyros-dev/pyros@29821f8

@asmodehn
Copy link
Member

There was a simple logic issue when determining which topic interface should be dropped or not.
Not sure how much this is related to our problem with the gateway, and if that fix will have any impact.

@stonier
Copy link
Collaborator Author

stonier commented Oct 26, 2016

Note...there is no gateway in a gopher_rocon launch and the multimaster subscriber problem is a different thing entirely - solely due to the list of subscribers from different masters.

@asmodehn
Copy link
Member

asmodehn commented Apr 6, 2017

@yotabits this should have been fixed a while ago from pyros. Can you confirm the fix please ? If the problem cannot be reproduced I will close it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants