-
Notifications
You must be signed in to change notification settings - Fork 252
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
Errors with latest Hubot version #19
Comments
Note: I am able to successfully get past this error locally on my Mac (10.7) by installing icu4c and linking it. If I run the bot in debug mode it shows that it successfully receives messages. However, it does not respond to messages. |
I get the same error locally and on Heroku but the bot still works as expected. Are you sure your |
@powdahound - Thanks very much for the response! Here's how I have these set:
In Hipchat the fullname field is
If I run the bot in DEBUG mode I can see it receiving XMPP traffic. Strangely, whether addressed in a room using @Robot or direct it won't answer any requests. I'll do some additional tests tonight, perhaps trying a different name and let you know what I find. |
Here's my debug output:
Strange that out> is empty in both cases. I gave the user ADMIN privleges in hip chat, still nothing. |
Odd... maybe it is something related to stringprep but I'm not sure. Probably worth putting some debug logging in the code if you have time to mess around with it. I'm much too busy at the moment. :( Btw admin privileges in HipChat doesn't change anything as far as basic chat functionality is concerned. |
I'm having the same issue, what I need to do to rebuild my bot with this latest fix? |
Just make sure you have the latest version of hubot and hubot-hipchat. |
aparently i'm using the last version and nothing. (btw, hosting at heroku) { "repository" : { "dependencies": { |
ok, fixed by adding "hubot-hipchat": "git://github.com/hipchat/hubot-hipchat.git#master". thanks |
I had to do the same thing. I wasn't familiar enough about NPM to suggest On Mon, Apr 9, 2012 at 3:45 PM, Tadeu <
|
Maybe it needs a new deploy to npm? (not familiar either) |
That's probably right. I always forget about npm. Will try to get it updated soon (I think I'm the owner of this package now...). |
1.0.4 pushed to npm - try that out. |
I am using 1.0.4 and still get the following error:
It doesn't look like it is causing problems, but couldn't find a good answer or reason as to why the error is coming up. I'm hosted on Heroku and this is a heroku error. |
Having the same problem here EDIT: turns out the error was a red herring, I turned on debug mode and I'm actually getting a jid-malformed error back. |
Yeah, the node-stringprep error does not actually cause trouble. If you're getting an error about an invalid JID it sounds like you haven't set your HUBOT_HIPCHAT_NAME properly. Make sure it matches the name on the account exactly. |
I'm getting the same error. With debug mode I'm seeing all the messages but the bot is deaf. It doesn't respond... |
I suspect this was actually caused by #49 |
👍 I too have missing |
The node-stringprep warning isn't known to be the cause of any issues. If you're having trouble, make sure to follow this repo's README to the letter. You could also try it with hubot 2.4.5 which is the latest I've tested with. Not sure if they broke anything in 2.4.6. |
Thanks, sure, it doesn't seem to cause any trouble right now, but I wanted to be sure that there would be no problems with it in future. |
Hi -
I'm receiving a strange error about node-stringprep. Google show this issue isn't new, though it appears to have been fixed in Issue #1 (#1). This is a new hubot I built it this evening using two sets of directions.
The first:
https://github.com/github/hubot/blob/master/src/templates/README.md
The second:
https://github.com/hipchat/hubot-hipchat
Here's the corresponding section of my logs:
Here's the relevant portion of my package.json:
Here's my heroku config (config masked to protect the innocent):
I'd appreciate any thoughts or advice.
The text was updated successfully, but these errors were encountered: