-
Notifications
You must be signed in to change notification settings - Fork 10.9k
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
Add internal hubot to private chats by default #7550
Comments
This was reported here : I would like to see the internal hubot in a private group - none of our groups are public |
I am experiencing this or similar on v0.57.2 - CentOS 6, Node 4.8.x If I create a Public channel I can add and chat to the internal hubot. |
Any thoughts on this form the rocket devs ? |
@MartinSchoeler |
Anyone looking at his ? Still exists on 0.58.2 |
also this seems not be fixed in 0.59.0-rc3 update: |
Still no progress with this ? |
Are there any technical limitation to support Hubot in the private chat??? |
@veerjainATgmail not as far as I am aware. If it works in a public chat I'd guess it should work in private. I'm still scratching my head as to why this bug is ignored for so long. It's irritating, and frustrating not to have the functionality. I'm no JS coder so not even sure where to start digging. Perhaps a dev will deign to shed some light on it? |
👍 Even using |
I assume you mean in a one on one conversation, because hubot works perfect in private rooms. |
No - the internal bot doesn't work in private rooms/groups. See #3132 as well, though I have not rested this Set a room to Public. Bot responds as expected. Set room to Private. Bot fails to respond at all. Set it back to Public and it responds again. This has been ongoing for several versions as far as I can see. |
I think I found where the problem is. If you open the internal hubot source code there is this function : const InternalHubotReceiver = (message) => {
if (DEBUG) { console.log(message); }
if (message.u.username !== InternalHubot.name) {
const room = RocketChat.models.Rooms.findOneById(message.rid);
if (room.t === 'c') {
const InternalHubotUser = new Hubot.User(message.u.username, {room: message.rid});
const InternalHubotTextMessage = new Hubot.TextMessage(InternalHubotUser, message.msg, message._id);
InternalHubot.adapter.receive(InternalHubotTextMessage);
}
}
return message;
}; You can see that there is a condition on the room type |
@ramrami seems to be the room type described here |
@eloo yes thank you. I think this should be added to the Internal Hubot as a setting. |
I just created an PR to solve this issue : #8933 |
What's the easiest way to do this guys and gals? Ideally it would be a default admin setting to toggle on or off (if on the hubot could repond to requests in every private chat until it's been removed from the chat.)
The text was updated successfully, but these errors were encountered: