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
After entering the command, Starting is printed, and every second it prints another . until the proxy has started, then it prints Running on a new line.
This was done because it might take the visor a while to get the needed transports and routes before even starting the proxy. So there would be no indication that anything was happening without even this simple logging.
When starting the proxy or VPN with skywire-cli it would be convenient if there was a flag to show the logging as it would print to the terminal if you were running the visor ; in order to have some idea of what was happening without needing the visor running in another terminal; or without needing to look anywhere else besides the terminal you are attempting to start the proxy or VPN in currently.
We should show only the logging specific to:
transport creation
route setup
the proxy or VPN starting
If invoked with the flag to show the logs ; it should:
keep logging from there, until you do ctrl+c
then stop the proxy or VPN.
With the flag that shows the logging, it should not give the terminal back until the proxy or VPN is stopped & it should be possible to stop it with ctrl+c
I recommend a similar flag to show logging for transport creation, at least.
The text was updated successfully, but these errors were encountered:
The following is currently observed when starting the proxy or VPN from
skywire-cli
:After entering the command,
Starting
is printed, and every second it prints another.
until the proxy has started, then it printsRunning
on a new line.This was done because it might take the visor a while to get the needed transports and routes before even starting the proxy. So there would be no indication that anything was happening without even this simple logging.
When starting the proxy or VPN with
skywire-cli
it would be convenient if there was a flag to show the logging as it would print to the terminal if you were running the visor ; in order to have some idea of what was happening without needing the visor running in another terminal; or without needing to look anywhere else besides the terminal you are attempting to start the proxy or VPN in currently.We should show only the logging specific to:
If invoked with the flag to show the logs ; it should:
ctrl+c
With the flag that shows the logging, it should not give the terminal back until the proxy or VPN is stopped & it should be possible to stop it with
ctrl+c
I recommend a similar flag to show logging for transport creation, at least.
The text was updated successfully, but these errors were encountered: