-
Notifications
You must be signed in to change notification settings - Fork 2.3k
-
Notifications
You must be signed in to change notification settings - Fork 2.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
0.5.3 release causes constant RTM reconnects #806
Comments
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...
|
@jayjanssen if you downgrade the 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 ***@***.***> 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>
.
|
This issue has been fixed in v0.5.4, now available on npm! |
I can confirm that 0.5.2 doesn't have this behavior.
This will keep going on.
The text was updated successfully, but these errors were encountered: