-
Notifications
You must be signed in to change notification settings - Fork 26
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
Error: read ECONNRESET #10
Comments
ECONNRESET means the other side of the TCP conversation abruptly closed its end of the connection. That particular error is typically generated from either the native node js http(s) libraries referenced in one of the dependent modules. It is not generated by Flint directly. If it is happening when Flint is requesting a URL from the spark API, it will likely be either be something with your connection, or the Spark API itself is having some issues. If it was a malformed request from Flint or your implementation of Flint, the error should be different. You can try to enable the debugs by starting your app with If you can share an example code where it is happening I can verify if it is related to Flint's code in any way. Feel free to email me at nmarus@gmail.com if you do not wish to share src here. |
Here is the code
|
Any idea ? :/ |
At what point do get that error? On running the app? or when running a particular "hears" command? |
This error appears randomly, sometimes, it appears when I start my bot, but more often, it appears when I don't speak to bot while twenty minutes approximately. I have the feeling that cloud9 turn the bot in idle. |
You can close this issue, this error no longer appears. |
Hello, I have an error with my bot but I don't understand why it is happened
The text was updated successfully, but these errors were encountered: