Hubot with Flowdock adapter launches but does not respond

[crfroehlich]

I get this behavior from OS X 10.9.2 (locally) and Windows 2012 (running on Azure). In both cases, I'm running:

Node 0.10.26 Hubot: 2.7.1 Flowdock-hubot: 0.6.0

Env. Vbl: PORT = 8181

I created a new gmail account with a first name of Hubot, added the user to my Flowdock organization with an alias of Hubot. I logged in as the user and verified that it could join a room.

I setup the environment variables (I neglected to do this the first time and got an exception to that effect), and I launch hubot bin\hubot.cmd -a flowdock. Hubot inits, and I can immediately hit http://localhost:8181/hubot/help and get a response.

There are no errors in the console/command prompt and no other content seems to be logged that I can find. Hubot seems to be functional, but there is no activity inside Flowdock. The user does not appear online and no variation of Hubot help will elicit a response. I get the same behavior in OS X as I do on Windows.

My hubot-scripts.json is empty. Here is my package.json:

 {
  "name": "Hubot",
  "version": "2.7.1",

  "author": "GitHub Inc.",

  "keywords": [
    "github",
    "hubot",
    "campfire",
    "bot"
  ],

  "description": "A simple helpful robot for your Company",

  "licenses": [{
    "type": "MIT",
    "url": "https://github.com/github/hubot/raw/master/LICENSE"
  }],

  "repository" : {
    "type": "git",
    "url": "https://github.com/github/hubot.git"
  },

  "dependencies": {
    "coffee-script": "1.6.2",
    "hubot-flowdock": ">= 0.6.0",
    "hubot":         ">= 2.6.0 < 3.0.0",
        "hubot-scripts": ">= 2.5.0 < 3.0.0"
  },

  "engines": {
    "node": ">= 0.8.x",
    "npm":  ">= 1.1.x"
  }
}

[anttipitkanen]

Is there anything in the hubot console output after start? It should print out an array of the flow UUIDs it has access to before it starts to listen to them. This is at least visible when foreman is used to run the bot.

Also, can you check that you can get a listing of flows for the hubot user using our REST API? You can do that with following request: (the @ in user email encoded as %40)

curl "https://user%40company.com:password@api.flowdock.com/flows"

[crfroehlich]

Ah hah! So executing the curl returned Access Denied. It occurred to me that I setup the Flockdock user using the Google authentication and that I had not set a separate password for Flowdock. Once I did that, the curl request returned the data you predicted.

I still do not see an array of flow UUIDs in the output, but hubot is now responding inside Flowdock! Perhaps clarify how to setup the Flowdock user in the instructions? I think I recall seeing someone else report that as the fault, but perhaps they were getting an actual exception which made it more obvious?

Fyi, here is the output (which is the same as before fixing the password):

F:\myBot>bin\hubot.cmd -a flowdock
[Tue Mar 04 2014 09:39:16 GMT-0800 (Pacific Standard Time)] DEBUG Loading adapte
r flowdock
[Tue Mar 04 2014 09:39:17 GMT-0800 (Pacific Standard Time)] DEBUG Loading script
s from F:\myBot\scripts
[Tue Mar 04 2014 09:39:17 GMT-0800 (Pacific Standard Time)] DEBUG Loading script
s from F:\myBot\src\scripts
[Tue Mar 04 2014 09:39:17 GMT-0800 (Pacific Standard Time)] DEBUG Parsing help f
or F:\myBot\scripts\events.coffee
[Tue Mar 04 2014 09:39:17 GMT-0800 (Pacific Standard Time)] DEBUG Parsing help f
or F:\myBot\scripts\google-images.coffee
[Tue Mar 04 2014 09:39:17 GMT-0800 (Pacific Standard Time)] DEBUG Parsing help f
or F:\myBot\scripts\help.coffee
[Tue Mar 04 2014 09:39:17 GMT-0800 (Pacific Standard Time)] DEBUG Parsing help f
or F:\myBot\scripts\httpd.coffee
[Tue Mar 04 2014 09:39:17 GMT-0800 (Pacific Standard Time)] DEBUG Parsing help f
or F:\myBot\scripts\maps.coffee
[Tue Mar 04 2014 09:39:17 GMT-0800 (Pacific Standard Time)] DEBUG Parsing help f
or F:\myBot\scripts\ping.coffee
[Tue Mar 04 2014 09:39:17 GMT-0800 (Pacific Standard Time)] DEBUG Parsing help f
or F:\myBot\scripts\pugme.coffee
[Tue Mar 04 2014 09:39:17 GMT-0800 (Pacific Standard Time)] DEBUG Parsing help f
or F:\myBot\scripts\roles.coffee
[Tue Mar 04 2014 09:39:17 GMT-0800 (Pacific Standard Time)] DEBUG Parsing help f
or F:\myBot\scripts\rules.coffee
[Tue Mar 04 2014 09:39:17 GMT-0800 (Pacific Standard Time)] DEBUG Parsing help f
or F:\myBot\scripts\storage.coffee
[Tue Mar 04 2014 09:39:17 GMT-0800 (Pacific Standard Time)] DEBUG Parsing help f
or F:\myBot\scripts\translate.coffee
[Tue Mar 04 2014 09:39:17 GMT-0800 (Pacific Standard Time)] DEBUG Parsing help f
or F:\myBot\scripts\youtube.coffee
[Tue Mar 04 2014 09:39:17 GMT-0800 (Pacific Standard Time)] DEBUG Loading hubot-
scripts from F:\myBot\node_modules\hubot-scripts\src\scripts
[Tue Mar 04 2014 09:39:17 GMT-0800 (Pacific Standard Time)] DEBUG Loading extern
al-scripts from npm packages

[anttipitkanen]

I added better instructions to the README about the password and added console logging for errors emitted from the underlying Flowdock session. That should display an error when the authentication fails due to invalid credentials. I released the changes as version 0.6.1.

For some reason, you seem to have completely different console output in the above log, so I'm not sure if the error message would have helped in your case.