-
Notifications
You must be signed in to change notification settings - Fork 95
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
Add timeout parameter #92
Add timeout parameter #92
Conversation
Signed-off-by: Ricardo Seriani <ricardo.seriani@gmail.com>
This PR should close #12 Please, check if it's working as it should. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Welcome to the project, @ricardoseriani. And thank you for your contribution.
It would be nice if the timeout value is persisted in the alias files when the user asks to create one:
$ mole -alias example1 -timeout 10s -v -local :8443 -remote :443 -server mole@example.com
$ cat ~/.mole.conf
[tunnels]
[tunnels.example1]
local = [":8443"]
remote = [":443"]
server = "mole@example.com"
key = ""
verbose = true
help = false
version = false
detach = false
timeout = 10s
Signed-off-by: Ricardo Seriani <ricardo.seriani@gmail.com>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do you mind adding timeout to the debug log that shows all CLI-related values? It's implemented on the String()
method of the type App
on cli/cli.go
. Thanks!
No problem. using:
|
Cool, thank you!
I see not problem on having the time expressed in nanoseconds so the decision to keep it or find a way to have the exact input will be up to you to decide :) |
Ok, thanks
About this, should I add the same timeout on the |
Yes, please! That helps on debugging issues. |
Signed-off-by: Ricardo Seriani <ricardo.seriani@gmail.com>
Thank you for your contribution, @ricardoseriani! |
Close #12
Signed-off-by: Ricardo Seriani ricardo.seriani@gmail.com