Skip to content
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

Open
rtvd opened this issue Apr 28, 2020 · 5 comments
Open

PIPE-CONNECT-FAIL test fails #174

rtvd opened this issue Apr 28, 2020 · 5 comments

Comments

@rtvd
Copy link

rtvd commented Apr 28, 2020

 Failure Details:
 --------------------------------
 PIPE-CONNECT-FAIL [Make sure a pipe connection fails]: 
      Unexpected Error: #<CL-ASYNC:STREAMISH-ERROR {1003DCDC13}>
#<STREAMISH-ERROR #<PIPE {1003DCD573}>: -2: ENOENT {1003DCDC13}>..
@rtvd
Copy link
Author

rtvd commented Apr 29, 2020

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.

@Plisp
Copy link
Contributor

Plisp commented Apr 29, 2020

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

@rtvd
Copy link
Author

rtvd commented Apr 29, 2020

Linux

@rtvd
Copy link
Author

rtvd commented Apr 29, 2020

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.

@rtvd
Copy link
Author

rtvd commented Apr 29, 2020

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants