Hubot - robot.http get method returns null body & res. Suspecting hubot timing out

[sggncucumber]

Hubo hear is invoking rest api (written node.js) which in turn returns the screenshot url post processing. Since the call would take few mins(3 mins max) hubot is timing out hence I am getting NULL body and res so I could not even check the status code or so.

How to fix the time out issue with hubot. Need your help at the earliest.

sample code,

robot.hear /(.*)command text/i, (res) ->
robot.http("http://localhost:9050/command")
.get() (err, res1, body) ->
res.reply "#{body}"

Here body is displaying as NULL in the rocket chat message. and suspecting the hubot's timeout. Your help is much appreciated...

Regards,
Ganesan S

[sggncucumber]

Following error is what I am getting as part of get method call...

Error: socket hang up

[sggncucumber]

Anybody there for the help!!!

[sggncucumber]

The flow is like this,

1. user would type the command in ROCKET CHAT
2. It would be heared by HUBOT which in turn calls another rest api (built on nodejs)
   Since node js would trigger the another script to get the result URL sometimes it would take more time to respond back.
3. If rest api takes more time then HUBOT simply timedout and return NULL as message body instead of resultant URL. However NodeJS works properly how it suppose to be.

Need your helpt o tweak the HUBOT so that it would wait for longer running scripts. Anything like timeout etc., at HUBOT end???

Your help is much appreciated!!!

[technicalpickles]

In general, it's important to do error handling when making http calls. body will be undefined if there's an error. See https://github.com/github/hubot/blob/master/docs/scripting.md#error-handling for some examples.

There's not a timeout as far that's hubot specific. robot.http is using https://github.com/technoweenie/node-scoped-http-client which is just a wrapper around the builtin http/https clients. There is a way to configure a timeout, but your code snippet didn't include it (just add .timeout(2000) for example).

It sounds like a problem with the rest API. Are you able to use the /command endpoint from something that isn't hubot?

[bostonaholic]

@technicalpickles When I add the timeout like you suggested I get the following error:

robot.http(url)
  .timeout(2000)
  .get() (err, res, body) ->

{ Error: socket hang up
  at createHangUpError (_http_client.js:302:15)
  at TLSSocket.socketCloseListener (_http_client.js:334:23)
  at emitOne (events.js:101:20)
  at TLSSocket.emit (events.js:191:7)
  at _handle.close (net.js:510:12)
  at TCP.done [as _onclose] (_tls_wrap.js:332:7)
 code: 'ECONNRESET' }

[technicalpickles]

@bostonaholic I would make sure you are able to use url from something aside from hubot, ie curl from the command line.

[bostonaholic]

@technicalpickles I can. And the code works fine without the .timeout. I want to add the timeout because the response can take a few seconds, maybe even up to 10, to respond sometimes.