0.5.3 release causes constant RTM reconnects

[jayjanssen]

I can confirm that 0.5.2 doesn't have this behavior.

bot    │ notice: [botkit] ** BOT ID: perconabottest ...attempting to connect to RTM!
bot    │ notice: [botkit] RTM websocket opened
bot    │ info: [slack] slack RTM connection durationMs=1504
...
bot    │ notice: [botkit] RTM close event: 1006 :
bot    │ error: [botkit] Abnormal websocket close event, attempting to reconnect
...
bot    │ notice: [botkit] ** BOT ID: bot ...reconnect attempt #1 of 3 being made after 1000ms
bot    │ notice: [botkit] ** BOT ID: bot ...attempting to connect to RTM!
bot    │ notice: [botkit] RTM websocket opened
...
bot    │ notice: [botkit] RTM close event: 1006 :
bot    │ error: [botkit] Abnormal websocket close event, attempting to reconnect
bot    │ notice: [botkit] ** BOT ID: bot ...reconnect attempt #1 of 3 being made after 1000ms
bot    │ notice: [botkit] ** BOT ID: bot ...attempting to connect to RTM!
bot    │ notice: [botkit] RTM websocket opened
...

This will keep going on.

[dasblitz]

Same here

[derekolson]

Was just about to post this same issue.

[peterswimm]

What happens if you set debug to true? Do you get any more information?

[benbrown]

This may be due to an update in the websocket library we use.

I am investigating!

[jayjanssen]

Trying, the 5MB of JSON data bot kit prints to debug on RTM connect isn't helping...

bot    │ notice: [botkit] RTM websocket opened
bot    │ debug: [botkit] RECEIVED MESSAGE
bot    │ debug: [botkit] CUSTOM FIND CONVO undefined
bot    │ debug: [botkit] DEFAULT SLACK MSG RECEIVED RESPONDER
bot    │ debug: [botkit] RECEIVED MESSAGE
bot    │ debug: [botkit] CUSTOM FIND CONVO { SLACK USER PROFILE JSON OF ONE MY TEAM MEMBERS }
bot    │ debug: [botkit] DEFAULT SLACK MSG RECEIVED RESPONDER
bot    │ debug: [botkit] RECEIVED MESSAGE
bot    │ debug: [botkit] CUSTOM FIND CONVO undefined
bot    │ debug: [botkit] DEFAULT SLACK MSG RECEIVED RESPONDER
bot    │ debug: [botkit] RECEIVED MESSAGE
bot    │ debug: [botkit] CUSTOM FIND CONVO U0AF9HFF1
bot    │ debug: [botkit] DEFAULT SLACK MSG RECEIVED RESPONDER
.... LOTS OF JSON ....
bot    │ notice: [botkit] RTM close event: 1006 :
bot    │ error: [botkit] Abnormal websocket close event, attempting to reconnect
bot    │ notice: [botkit] ** BOT ID: bot ...reconnect attempt #1 of 3 being made after 1000ms
bot    │ debug: [botkit] rtm.start no_unreads=true, simple_latest=true, token=MY TOKEN
bot    │ info: [botkit] ** API CALL: https://slack.com/api/rtm.start



bot    │ notice: [botkit] RTM close event: 1006 :
bot    │ error: [botkit] Abnormal websocket close event, attempting to reconnect
bot    │ notice: [botkit] ** BOT ID: bot ...reconnect attempt #1 of 3 being made after 1000ms
bot    │ info: [botkit] ** API CALL: https://slack.com/api/rtm.start
bot    │ debug: [botkit] rtm.start no_unreads=true, simple_latest=true, token=MY TOKEN

[benbrown]

@jayjanssen if you downgrade the ws dependency back to 1.1.1, it should work.

not sure why this is breaking yet, but it appears to be related to that dependency.

[jayjanssen]

it's not urgent enough for me to build my own custom version. I'm happy to test any new releases you come up with though.

[peterswimm]

With the help of Slack team, we think we have a fix for this, coming soon!

#808

[anurag-saran]

I am seeing this issue with "botkit": "^0.5.1" and "botkit": "^0.5.0" versions too.

[anurag-saran]

By when are we expecting to get a fix ?

[jayjanssen]

@anurag-saran I would expect "^0.5.1" and "^0.5.0" to upgrade to the latest in the 0.5.x series. Try just "0.5.2" without the ^

[anurag-saran]

Perfect this fixed the issue. Thanks a ton.

…

On Fri, Apr 28, 2017 at 7:41 AM, Jay Janssen ***@***.***> wrote: @anurag-saran <https://github.com/anurag-saran> I would expect "^0.5.1" and "^0.5.0" to upgrade to the latest in the 0.5.3 series. Try just "0.5.2" without the ^ — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#806 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAqbemOAUdOtP6o9xUfjuf2XGCGGhudjks5r0dBagaJpZM4NKath> .

[benbrown]

This issue has been fixed in v0.5.4, now available on npm!