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

Can't read Unix domain socket as a file #364

Open
AlexCannonball opened this issue Jan 28, 2024 · 0 comments
Open

Can't read Unix domain socket as a file #364

AlexCannonball opened this issue Jan 28, 2024 · 0 comments

Comments

@AlexCannonball
Copy link

Hello,

This issue is related to #327

I've got some progress researching a way to pass a file to protolint w/o creating a temp file.

I use Node.js IPC connections (https://nodejs.org/docs/latest-v18.x/api/net.html#identifying-paths-for-ipc-connections) and it works fine on Windows.

Unfortunately when testing on WSL + Ubuntu 22 it doesn't work:

  • Node.js creates a Unix domain socket. It's displayed via ls:
    cannonball@DESKTOP:/run/user/1000$ ls -l /run/user/1000/
    total 0
    srwxr-xr-x 1 cannonball cannonball   0 Jan 28 23:35 foo.proto
    
  • I can read the text from the socket via shell with nc -U foo.proto.
  • When I attempt running protolint, it exits with status code 2:
    '2024/01/28 23:15:52 [INFO] protolint doesn't load a config file\nopen /run/user/1000/foo.proto: no such device or address\n'
    

Unlike Windows, I don't see any attempts to connect to the socket. Is protolint supposed to read from Unix domain sockets?

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

1 participant