-
Notifications
You must be signed in to change notification settings - Fork 45
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
Assertion `status == 0’ failed #82
Comments
Can you provide a reproducible test for this? What platform did you encounter this on? |
Sorry for the delay in reply. The platform is:
I am using cap as part of complex application. Thus I'll try to to create an isolated test case. Generally, I am wondering why |
What node version and |
Also, does simply commenting out the offending line out fix the issue or cause other problems? It would be interesting to know what the |
…en error occurs, issue mscdex#82
…en error occurs, issue mscdex#82
I think, socket errors need to be properly handled similar to the cases reported earlier. See #23 and #26
The text was updated successfully, but these errors were encountered: