PIPE-CONNECT-FAIL test fails about cl-async HOT 5 OPEN

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 mkfifo?

You can see this example in C.

from cl-async.

This library wraps libuv, which is a wrapper over OS-specific i/o interfaces. What OS are you running?

from cl-async.

Linux

from cl-async.

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.

from cl-async.

Ah... I've found libuv's list of errors.

from cl-async.