-
Notifications
You must be signed in to change notification settings - Fork 887
coder ping
UX concerns
#14752
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
Comments
These both sound reasonable, although this would of course mean any diagnostics we determine would always get shown. We currently don't show them if a direct connection was established, as to avoid overloading the user with warnings when their connection is already preferable. We could continue to do that, but the diagnostics would need to come after the pings + ctrl+c? |
Since we need to do pings to determine whether we got p2p or not we definitely need to put the diagnostics last. We can make them get written after you hit ctrl+c or after the |
Can we do one silent ping to show diagnostics and then print the rest? |
ping
command runs forever.coder ping
goes for 10 round trips by default, which seems arbitrary and often frustrates me.ping
running forever is a feature not a bug. It means I can leave it up on a terminal to monitor my network conditions for a long time. When I ctrl+c oncoder ping
I want a statistical summary just likeping
.-n
approaches infinity.cc @ethanndickson
The text was updated successfully, but these errors were encountered: