-
Notifications
You must be signed in to change notification settings - Fork 36
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
Exited(255) Unhandled exception: SocketException: Write failed (OS Error: Broken pipe, errno = 32), address = 127.0.0.1, port = 63467 #49
Comments
I think that you need are missing appropriate error catching. What you receive is exception of type SocketException that is result of disconnect. What do you to expect from this redis-dart library when redis service shuts down unexpectedly and socket is shut down? |
That is interesting. I will try to take deeper look later when I will have more time. Thank You for your report. |
I have now repeated similar issue on with similar approach using StreamQueue<T> as I wanted to replace StreamNext hoping for better results. To test this, you need tcp echo server (not included here) and and than kill server after running this dart script Here is ouput error Has anyone have idea what is going on. Otherwise I will try to find support with dart support. |
I have reported this behavior at dart-sdk dart-lang/sdk#47538 and you can follow and contribute as we are learning what is going on. |
Thanks sir,Ancestral blessing, I hope it can be solved as soon as possible!😊 |
There is simple patch available for dart. |
We have got some response from Dart and there is workaround. One needs to close socket just when error is received. This workaround is now implemented in master branch and will be released in next days. Please test and report if you have issues. |
Fixed and released whit v2.2.0. Thank you for your input. |
Thanks sir,I tested it and it has been repaired. |
Occurs when the redis service shuts down unexpectedly!
=====================================================================================
The text was updated successfully, but these errors were encountered: