Adapter disconnects after a period of time about lita-slack

[jimmycuadra]

What a frustrating issue. This is the first I'm hearing of it. I wonder if other people are experiencing this and haven't reported it, or if there's something unique to your setup. In either case, seems like the adapter should provide more debugging information, perhaps leveraging any ability Faye has to let you log the websocket activity.

[Ginja]

@jimmycuadra that would be great. I've also opened up an issue with Slack and they're looking at their logs. I'll update this PR if they come up with anything.

[pseidemann]

I experience the same issues.

here is the log with log level debug:

[2015-12-14 18:10:48 UTC] DEBUG: Connecting to the Slack Real Time Messaging API.
[2015-12-14 18:10:48 UTC] DEBUG: Connected to the Slack Real Time Messaging API.
[2015-12-14 18:10:49 UTC] INFO: Connected to Slack.
[2015-12-14 18:10:49 UTC] DEBUG: presence_change event received from Slack and will be ignored.
[2015-12-14 18:10:49 UTC] DEBUG: presence_change event received from Slack and will be ignored.
[2015-12-14 18:11:04 UTC] DEBUG: presence_change event received from Slack and will be ignored.
[2015-12-14 18:11:44 UTC] DEBUG: user_typing event received from Slack and will be ignored.
[2015-12-14 18:11:48 UTC] DEBUG: user_typing event received from Slack and will be ignored.
[2015-12-14 18:11:51 UTC] DEBUG: user_typing event received from Slack and will be ignored.
[2015-12-14 18:11:56 UTC] DEBUG: user_typing event received from Slack and will be ignored.
[2015-12-14 18:12:00 UTC] DEBUG: user_typing event received from Slack and will be ignored.
[2015-12-14 18:12:01 UTC] DEBUG: presence_change event received from Slack and will be ignored.
[2015-12-14 18:12:01 UTC] DEBUG: presence_change event received from Slack and will be ignored.
[2015-12-14 18:12:03 UTC] DEBUG: presence_change event received from Slack and will be ignored.
[2015-12-14 18:12:03 UTC] DEBUG: presence_change event received from Slack and will be ignored.
[2015-12-14 18:12:04 UTC] DEBUG: user_typing event received from Slack and will be ignored.
[2015-12-14 18:12:05 UTC] DEBUG: Dispatching message to Lita from UXXXX.
[2015-12-14 18:12:12 UTC] DEBUG: user_typing event received from Slack and will be ignored.
[2015-12-14 18:12:13 UTC] DEBUG: Dispatching message to Lita from UYYYY.
[2015-12-14 18:12:32 UTC] DEBUG: user_typing event received from Slack and will be ignored.
[2015-12-14 18:13:45 UTC] DEBUG:  event received from Slack and will be ignored.
[2015-12-14 18:13:45 UTC] INFO: Disconnected from Slack.
[2015-12-14 18:13:45 UTC] DEBUG: Closing connection to the Slack Real Time Messaging API.

I never see messages sent by response.reply(...) from the bot and it disconnects after a couple of minutes. it worked just fine until 2015-12-14 12:30:00 UTC.

in the log there is one interesting line:

[2015-12-14 18:13:45 UTC] DEBUG:  event received from Slack and will be ignored.

it seems like it gets some event it can't parse. maybe this is related?

[NikolayRys]

me too:

$ bundle exec lita
[2015-12-15 05:05:43 UTC] INFO: Connected to Slack.
[2015-12-15 05:15:52 UTC] INFO: Disconnected from Slack.

[m-funky]

me too

[2015-12-14 05:53:20 UTC] DEBUG: Connecting to the Slack Real Time Messaging API.
[2015-12-14 05:53:21 UTC] DEBUG: Connected to the Slack Real Time Messaging API.
[2015-12-14 05:53:21 UTC] INFO: Connected to Slack.
[2015-12-14 05:53:21 UTC] DEBUG: presence_change event received from Slack and will be ignored.
[2015-12-14 05:53:21 UTC] DEBUG: presence_change event received from Slack and will be ignored.
[2015-12-14 05:53:21 UTC] DEBUG: presence_change event received from Slack and will be ignored.
[2015-12-14 05:53:53 UTC] DEBUG: presence_change event received from Slack and will be ignored.
[2015-12-14 05:53:54 UTC] DEBUG: presence_change event received from Slack and will be ignored.
[2015-12-14 05:54:12 UTC] DEBUG: presence_change event received from Slack and will be ignored.
[2015-12-14 05:55:03 UTC] DEBUG: presence_change event received from Slack and will be ignored.
[2015-12-14 05:55:08 UTC] DEBUG: user_typing event received from Slack and will be ignored.
[2015-12-14 05:55:10 UTC] DEBUG: Dispatching message to Lita from UXXXXXX.
[2015-12-14 05:55:50 UTC] DEBUG: presence_change event received from Slack and will be ignored.
[2015-12-14 05:55:52 UTC] DEBUG: presence_change event received from Slack and will be ignored.
[2015-12-14 05:56:03 UTC] INFO: Disconnected from Slack.
[2015-12-14 05:56:03 UTC] DEBUG:  event received from Slack and will be ignored.
[2015-12-14 05:56:03 UTC] DEBUG: Closing connection to the Slack Real Time Messaging API.

from 12/10

[jimmycuadra]

For everyone replying saying they are experiencing this issue, which of these is true for you?

1. You've been using Lita for a while and this started happening recently.
2. You've been using Lita for a while and this has always happened.
3. You just started using Lita and this has always happened.

Where "a while" is somewhere on the order of many weeks or more.

[NikolayRys]

It's the third one in my case.

[m-funky]

My case is 1.
I've been using Lita for 10 months.

[Ginja]

1 as well.

[pseidemann]

1 for me

[pseidemann]

my bot still can't send any message since monday. I've implemented my own handlers like in this example http://docs.lita.io/plugin-authoring/handlers/#examples, response.reply() gets called with a proper string but nothing appears in the slack channel. I didn't changed anything in the code. using the latest lita and lita-slack gems didn't helped.

was there some major change in the slack api or something?

[Ginja]

I've passed along this GitHub issue to Slack's support, and they're passing it along to their engineers. I'll update this thread when they get back to me.

[jimmycuadra]

Thank you, Ginja. As dismissive as it sounds to say "this is probably a Slack issue," it very well may be, so let's see what they say.

[dwradcliffe]

Me too, situation 1. Lita is receiving messages from slack for a few minutes but no responses ever make it back to Slack. After 2-3 minutes it crashes.

[v-fedorov]

Having the exact same issue

[dwradcliffe]

Ours started working again. I wonder if something changed on the Slack side?

[pseidemann]

I can confirm mine started working again, too

[Ginja]

Same here. I updated our ticket to Slack's support and this was their response:

Strange, no changes were made to specifically address this issue but it's possible that something went out that had an effect. I would ask though that if you see this come up again to let me know right away — it always feels a little uneasy when something fixes itself!

@jimmycuadra could we leave this issue open as a reminder to add some debugging options for faye-websocket?

[jimmycuadra]

Yes, definitely. Thanks for following up, everyone!

[jimmycuadra]

I'm gonna close this, but those interested in tracking additional debugging output for the adapter can follow #32.