You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The --retrieve option is not being parsed correctly.
$ portastic find 3000 3100 -r 1
Unhandled rejection Error: listen EACCES 0.0.0.0:1
at Object.exports._errnoException (util.js:870:11)
at exports._exceptionWithHostPort (util.js:893:20)
at Server._listen2 (net.js:1224:19)
at listen (net.js:1273:10)
at net.js:1382:9
at nextTickCallbackWith3Args (node.js:452:9)
at process._tickCallback (node.js:358:17)
Unhandled rejection Error: listen EACCES 0.0.0.0:1
at Object.exports._errnoException (util.js:870:11)
at exports._exceptionWithHostPort (util.js:893:20)
at Server._listen2 (net.js:1224:19)
at listen (net.js:1273:10)
at net.js:1382:9
at nextTickCallbackWith3Args (node.js:452:9)
at process._tickCallback (node.js:358:17)
The type appears to be missing in the option declaration which looks to be the problem. I'll create a PR to address the issue.
Related, the --retrieve option for find could probably stand to have some documentation to go along with it. I saw the API had the option available and only realized the CLI did as well when taking a look at the source. It looks like this might be a limitation of the commander library when options are defined for commands.
In any case, good work on the lib, it was exactly what I was looking for ;-)
The text was updated successfully, but these errors were encountered:
greaterweb
added a commit
to greaterweb/node-portastic
that referenced
this issue
Mar 25, 2016
The
--retrieve
option is not being parsed correctly.The type appears to be missing in the option declaration which looks to be the problem. I'll create a PR to address the issue.
Related, the
--retrieve
option forfind
could probably stand to have some documentation to go along with it. I saw the API had the option available and only realized the CLI did as well when taking a look at the source. It looks like this might be a limitation of the commander library when options are defined for commands.In any case, good work on the lib, it was exactly what I was looking for ;-)
The text was updated successfully, but these errors were encountered: