oriuminc / pantzbot

A Hubot instance
2 stars 0 forks source link

`call set <url>` isn't working on #slack #1

Open patcon opened 11 years ago

patcon commented 11 years ago

Here are the heroku logs when I'm typing the commands in chat:

:48.661122+00:00 app[web.1]: Incoming message received
2013-10-08T14:27:48.661527+00:00 app[web.1]: Received slackbot: call set <a href="http://homestarrunner.com">homestarrunner.com</a> from patcon
2013-10-08T14:27:55.991097+00:00 app[web.1]: Received slackbot: call me from patcon
2013-10-08T14:27:55.990608+00:00 app[web.1]: Incoming message received
2013-10-08T14:27:55.992650+00:00 app[web.1]: Sending message
2013-10-08T14:27:56.010970+00:00 heroku[router]: at=info method=POST path=/hubot/slack-webhook host=pantzbot.herokuapp.com fwd="54.221.104.139" dyno=web.1 connect=2ms service=35ms status=200 bytes=5
2013-10-08T14:27:56.177367+00:00 app[web.1]: Incoming message received
2013-10-08T14:27:56.177367+00:00 app[web.1]: Received Click here for hubot-testing video chat: undefined from slackbot
2013-10-08T14:27:56.177411+00:00 heroku[router]: at=info method=POST path=/hubot/slack-webhook host=pantzbot.herokuapp.com fwd="54.221.104.139" dyno=web.1 connect=2ms service=4ms status=200 bytes=5
2013-10-08T14:28:10.928081+00:00 heroku[router]: at=info method=POST path=/hubot/slack-webhook host=pantzbot.herokuapp.com fwd="54.221.104.139" dyno=web.1 connect=1ms service=14ms status=200 bytes=5
2013-10-08T14:28:10.925442+00:00 app[web.1]: Incoming message received
2013-10-08T14:28:10.925442+00:00 app[web.1]: Received slackbot: call set homestarrunner from patcon
2013-10-08T14:28:13.150151+00:00 app[web.1]: Incoming message received
2013-10-08T14:28:13.150249+00:00 app[web.1]: Received slackbot: call me from patcon
2013-10-08T14:28:13.150392+00:00 app[web.1]: Sending message
2013-10-08T14:28:13.379028+00:00 app[web.1]: Incoming message received
2013-10-08T14:28:13.379132+00:00 app[web.1]: Received Click here for hubot-testing video chat: undefined from slackbot

There are not errors, and it looks like it's being set correctly, but guessing that the slack adapter is leading to quirky results with the lookup. Perhaps something hardcoded about expecting a "#" at the beginning of channels, or something like that.

I'm not particularly affected by this, so won't be working on it. But wanted to doc the issue.

cc: @emarchak @DavidSabine