Slack adapter and hubot-apiai: sessionId Parameter

[dakky]

Hello:

when using the slackadapter and api.ai i get the following error:
[Thu Oct 05 2017 12:10:00 GMT+0200 (CEST)] DEBUG Calling API.AI with 'hello' and session undefined [...] statusCode: 400, responseBody: '{\n "id": "xxx-xxxx-xxxx",\n "timestamp": "2017-10-05T10:09:12.366Z",\n "lang": "en",\n "status": {\n "code": 400,\n "errorType": "bad_request",\n "errorDetails": "Required \'sessionId\' parameter is empty."\n }\n}', name: 'ServerError', message: 'Wrong response status code.' }

when modifing the following line:

hubot-apiai/src/apiai.coffee

Line 36 in 0237d1d

else if robot.adapterName == 'slack'

to = "slackx" and forcing the fallback mechanism, it works fine. Any idea whats wrong there?

[ojacques]

Thanks for reporting this @dakky ! I am not sure what's wrong. If you find out, a pull request would be great!

[divyangjp]

@ojacques @dakky When it's the first message, thread_ts value is undefined. If you start a thread with the message, thread_ts gets populated, and hence the error goes away.

[divyangjp]

@ojacques I assume flowdock assigns thread_ts value even to the messages without the threads.
Maybe this needs a fix for Slack

[ojacques]

@divyangjp I don't use Slack, so, I can't tell. However, if you find a way to get this right, that'd be really nice...

[adriantan08]

Hi. I think there might be some changes in the response object Slack sends. rawMessage.thread_ts is no longer existing.

Could be rawMessage.ts?

[kavya05]

@adriantan08 did the change work for you? i mean are u able to integrate with slack?

[kavya05]

hey guys it worked for me when i made these changes

but its creating a mess by calling the same statement again and again, its not a good practice to use this