Skip to content

exit if the user has requested a specific port#954

Merged
joehand merged 3 commits intodat-ecosystem:masterfrom
SvenDowideit:error-out-on-sepecifed-port
Jul 5, 2018
Merged

exit if the user has requested a specific port#954
joehand merged 3 commits intodat-ecosystem:masterfrom
SvenDowideit:error-out-on-sepecifed-port

Conversation

@SvenDowideit
Copy link
Copy Markdown
Contributor

Signed-off-by: Sven Dowideit sven.dowideit@csiro.au

for #945

to go with dat-ecosystem-archive/dat-node#192

@SvenDowideit
Copy link
Copy Markdown
Contributor Author

I tried to work out how to use the lib/exit.js code, but couldn't figure out a way that worked.

@SvenDowideit SvenDowideit force-pushed the error-out-on-sepecifed-port branch from d07902f to a02ca0f Compare March 7, 2018 04:35
bin/cli.js Outdated
{ name: 'dir', abbr: 'd', help: 'set the directory for Dat' },
{ name: 'logspeed', default: 400 },
{ name: 'port', default: 3282, help: 'port to use for connections' },
{ name: 'port', default: 0, help: 'port to use for connections (tries 3282 by default)' },
Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think we'd be better removing this default. Otherwise dat-node won't try 3282 first.

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Oh no it'll try 3828 first, nm. But still not sure we need this, just confuses things =).

@joehand
Copy link
Copy Markdown
Collaborator

joehand commented Mar 8, 2018

I tried to work out how to use the lib/exit.js code, but couldn't figure out a way that worked.

Cool, I can take a look at adding that.

@joehand
Copy link
Copy Markdown
Collaborator

joehand commented Mar 8, 2018

Can you check out these syntax changes

@joehand joehand added this to the 13.11 milestone Mar 8, 2018
Signed-off-by: Sven Dowideit <sven.dowideit@csiro.au>
@SvenDowideit SvenDowideit force-pushed the error-out-on-sepecifed-port branch from a02ca0f to 0eaa0d5 Compare March 11, 2018 23:13
@SvenDowideit
Copy link
Copy Markdown
Contributor Author

@joehand nice! thanks for the syntax pointer.

is there a test exception that can be configured for import-progress.js? to my naive reading, that seems like a false negative.

@joehand
Copy link
Copy Markdown
Collaborator

joehand commented Mar 23, 2018

is there a test exception that can be configured for import-progress.js? to my naive reading, that seems like a false negative.

ya not sure what was going on there. Made it one-liner to avoid indent error.

@joehand joehand merged commit 9ac2d07 into dat-ecosystem:master Jul 5, 2018
@SvenDowideit SvenDowideit deleted the error-out-on-sepecifed-port branch July 6, 2018 03:48
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

Successfully merging this pull request may close these issues.

2 participants