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

ENOENT when running on windows #4

Closed
Pomax opened this issue Oct 18, 2019 · 3 comments
Closed

ENOENT when running on windows #4

Pomax opened this issue Oct 18, 2019 · 3 comments

Comments

@Pomax
Copy link

Pomax commented Oct 18, 2019

after cloning, renaming to lightroom-catalog-helper, and running npm install, running npm start on Windows 10 x64 leads to the following error:

C:\Users\Pomax\Documents\Git\projects\lightroom-catalog-helper>npm start

> electron-with-server-example@1.0.0 start C:\Users\Pomax\Documents\Git\projects\lightroom-catalog-helper
> electron .


 checking 1
Service path not specified, so defaulting to ipc.config.socketRoot + ipc.config.appspace + id
requested connection to  myapp1 /tmp/app.myapp1
Connecting client on Unix Socket : /tmp/app.myapp1


######
error:  { Error: connect ENOENT \\.\pipe\tmp-app.myapp1
    at PipeConnectWrap.afterConnect [as oncomplete] (net.js:1061:14)
  errno: 'ENOENT',
  code: 'ENOENT',
  syscall: 'connect',
  address: '\\\\.\\pipe\\tmp-app.myapp1' }
found socket 1
connection closed myapp1 /tmp/app.myapp1 Infinity tries remaining of Infinity
Yuki exceeded connection rety amount of  or stopRetrying flag set.

(Yuki being the machine name for this particular Win10 installation)

@Pomax
Copy link
Author

Pomax commented Oct 18, 2019

I don't actually know what to make of this error - the actual electron app and server window start up "just fine" from what I can tell, and the factorial/phone buttons work.

@jlongster
Copy link
Owner

Sorry for the delay, haven't been checking github!

This is from findOpenSocket: https://github.com/jlongster/electron-with-server-example/blob/master/find-open-socket.js. It works by trying to connect to an existing socket to "probe" it. If there's nothing running there, it knows it's free.

I fixed in Actual long ago, and just copied over the relevant fix here: 7afdab9

@Pomax
Copy link
Author

Pomax commented Jan 4, 2020

nice, cheers

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