-
Notifications
You must be signed in to change notification settings - Fork 40
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
PIPE-CONNECT-FAIL test fails #174
Comments
I do not see how the pipe code is supposed to work. It appears to be using named pipes but if it does, where does it call You can see this example in C. |
This library wraps libuv, which is a wrapper over OS-specific i/o interfaces. What OS are you running? |
Linux |
Unfortunately there is little documentation on which conditions can/should be raised. I have raised a ticket for that - #175. The root cause appears to be that functions from cl-libuv are called but their return values are not checked. I could have added the checks but it is not clear to me which conditions are supposed to be raised in cl-async. Also, I do not see any documentation on the return values reported by libuv. |
Ah... I've found libuv's list of errors. |
The text was updated successfully, but these errors were encountered: