Skip to content
This repository has been archived by the owner on Jun 4, 2022. It is now read-only.

Lumo shouldn't crash if it can't bind to socket REPL port #159

Closed
anmonteiro opened this issue May 3, 2017 · 0 comments
Closed

Lumo shouldn't crash if it can't bind to socket REPL port #159

anmonteiro opened this issue May 3, 2017 · 0 comments

Comments

@anmonteiro
Copy link
Owner

anmonteiro commented May 3, 2017

Lumo socket REPL listening at localhost:555.
cljs.user=> events.js:163
      throw er; // Unhandled 'error' event
      ^

Error: listen EACCES 127.0.0.1:555
    at Object.exports._errnoException (util.js:1050:11)
    at exports._exceptionWithHostPort (util.js:1073:20)
    at Server.setupListenHandle [as _listen2] (net.js:1247:19)
    at listenInCluster (net.js:1304:12)
    at doListen (net.js:1428:7)
    at GetAddrInfoReqWrap.asyncCallback [as callback] (dns.js:62:16)
    at GetAddrInfoReqWrap.onlookup [as oncomplete] (dns.js:78:10)
@anmonteiro anmonteiro changed the title Lumo shouldn't crash if can't bind to port Lumo shouldn't crash if it can't bind to socket REPL port May 3, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

1 participant