You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This ended up being the root cause of what looks like a bunch of similar issues to #80 , when digging through the contents of brain and adding a bunch of logging to getUserForName, I discovered that hipchat assigns different identifiers for users in each room, as well as in 1:1 chat. The user as identified in a room roster has mention information, whereas the 1:1 does not. I'm still trying to see if this is part of the hipchat xmpp protocol or part of the hubot-hipchat adapter.
Brain.getUserForName does not break out of its loop when it finds the first user, so as the count of user objects grows over time, the behavior does not remain consistent for any given user.
This ended up being the root cause of what looks like a bunch of similar issues to #80 , when digging through the contents of brain and adding a bunch of logging to getUserForName, I discovered that hipchat assigns different identifiers for users in each room, as well as in 1:1 chat. The user as identified in a room roster has mention information, whereas the 1:1 does not. I'm still trying to see if this is part of the hipchat xmpp protocol or part of the hubot-hipchat adapter.
Brain.getUserForName does not break out of its loop when it finds the first user, so as the count of user objects grows over time, the behavior does not remain consistent for any given user.
The text was updated successfully, but these errors were encountered: