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.
Same here
Was just about to post this same issue.
What happens if you set debug to true? Do you get any more information?
This may be due to an update in the websocket library we use.
I am investigating!
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
@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.
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.
With the help of Slack team, we think we have a fix for this, coming soon!
I am seeing this issue with "botkit": "^0.5.1" and "botkit": "^0.5.0" versions too.
By when are we expecting to get a fix ?
@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 ^
Perfect this fixed the issue. Thanks a ton.
On Fri, Apr 28, 2017 at 7:41 AM, Jay Janssen notifications@github.com
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
https://github.com/howdyai/botkit/issues/806#issuecomment-297976768, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAqbemOAUdOtP6o9xUfjuf2XGCGGhudjks5r0dBagaJpZM4NKath
.
This issue has been fixed in v0.5.4, now available on npm!
Most helpful comment
This issue has been fixed in v0.5.4, now available on npm!