search

atmos / hubot-gtalk

GTalk adapter for Hubot
MIT License
14 stars 6 forks source link

ERROR Cannot load adapter gtalk - Error: Cannot find module 'hubot' #4

Closed payneio closed 12 years ago

payneio commented 12 years ago

Using hubot 2.1.3.

Updated dependencies: "dependencies": { "hubot-irc": ">= 0.0.1", "hubot": ">= 2.0.0", ... }

Ran: npm install

When starting hubot:

TypeError: Cannot call method 'on' of null at Object. (/opt/hubot/bin/hubot:105:19) at Object. (/opt/hubot/bin/hubot:109:4) at Module._compile (module.js:444:26) at Object.run (/usr/local/lib/node_modules/coffee-script/lib/coffee-script/coffee-script.js:68:25) at /usr/local/lib/node_modules/coffee-script/lib/coffee-script/command.js:135:29 at /usr/local/lib/node_modules/coffee-script/lib/coffee-script/command.js:110:18 at [object Object]. (fs.js:115:5) at [object Object].emit (events.js:64:17) at afterRead (fs.js:1111:12) at Object.wrapper as oncomplete

atmos commented 12 years ago

Use the released version of hubot, not a checkout of the repo. You can get the working version from http://hubot.github.com

payneio commented 12 years ago

Ok. This works better now. I installed hubot-2.1.3.tar.gz, added the "hubot-gtalk": ">= 0.0.1" depencency to package.json and re-ran npm-install. bin/hubot now works as a local test. Also, my bot shows up in gtalk. However, it doesn't respond to anything?? Perhaps this has to do with node-stringprep configure/building successfully each time I start up? Any tips on troubleshooting why my bot connects but won't respond?

payneio commented 12 years ago

My bot was responding... just not to the right name! Must have been using old gtalk adapter source. I figured out the robot name was hard coded as "Hubot" instead of the current @robot.name. Once I updated this, my bot now responds.

atmos commented 12 years ago

Great!

Bankq commented 12 years ago

I meet the same issue now and I don't think it's robot's name's issue. Any one can help?

Thanks!