-
Notifications
You must be signed in to change notification settings - Fork 663
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
StateMachine: unhandled event 'websocket close' in state 'connecting' #531
Comments
thanks for reporting @malonecm this sounds like its potentially related to #527, since they both have to do with the websocket being in a closing state unexpectedly. we're a little low on data around how this would happen, but that stack trace is definitely useful, thanks for that. are you able to increase the |
I've enabled debug logLevel now. If I get another StateMachine issue with websocket close I will post more logs. Thank you! |
Different crash this time. Debug log doesn't seem to help much to me. The "goodbye" thing I had never noticed before.
|
And still leaving debug on looking for the first one. If adding this onto this is inappropriate I can open a different issue. Just let me know. Thank you! |
@malonecm looks like you found another issue to me. the new one seems a little more insidious, too. for this second one, it would be useful to see the log statements from the |
it looks like the OP in #527 also had a similar issue with |
we think v4.2.0 fixes this issue. please update and give it a try! if not' feel free to comment and we'll reopen. |
@malonecm have you tried v4.2.0? Any better than the previous version? At the very least, we should have more meaningful logs now. |
Yeah, I did upgrade. I have no seen any further crashes. I do still have debug logging on. If I see anything I will let you guys know! |
Not sure if this is the same reason but same crash on @slack in socket mode.
This happened right before that
|
Hello, we also faced the issue logs:
|
We are facing this issue recently, too. Is there any updates or workaround to surpress this error? |
Description
Have an always running bot. Had a random crash on 4.1.0 today. Trace follows, which hopefully will help. Not really reproducible. Hopefully just a state transition missing in your state machine.
/opt/local/slack-bot/node_modules/finity/lib/core/StateMachine.js:76
What type of issue is this?
Requirements
Bug Report
Filling out the following details about bugs will help us solve your issue sooner.
Reproducible in:
@slack/client
version: 4.1.0node version: v8.10.0
OS version(s): Amazon Linux (4.9.76-38.79.amzn2.x86_64)
Steps to reproduce:
Expected result:
From the error, it sounds like the websocket should just attempt to restart itself if it gets a close while it is connecting.
Actual result:
Node crashed and systemd restarted it, resulting in very small downtime
Attachments:
None
The text was updated successfully, but these errors were encountered: