-
Notifications
You must be signed in to change notification settings - Fork 224
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
[Suggestion] Suppress error output when GitHub version check fails #874
Comments
This looks like the error was generated from an incorrectly configured HTTP PROXY? Given the URL is reported as 127.0.0.1? Should we keep this around and see if anyone else is affected? If you want to silently fail the error, I'm OK with that too, and perhaps set a shorter timeout at the same time. |
I'm a nixpkgs maintainer, and I'm struggling to avoid triggering this network error when looking up version of
If there is a solution to this, I'd like to know. (So I can properly fix the package.) Thank you. |
Hi @superherointj would a flag like cc @welteki (who also maintains Nix packages AFAIK) Alex |
Thanks for the prompt answer. Would |
There is already a flag to skip the check.
When this is used there should not be any network communication. |
I see. Thanks. |
@rgee0 can we close the issue? |
Up to you. |
Expected Behaviour
The
faas-cli
failing to check whether it is the latest version does not affect the operation of the downloaded binary. If an error is encountered encourage the user to check manually, rather than distracting them with a verbose error message.Current Behaviour
This is a forced error, so somewhat contrived, however a screenshot from a user is shown below:
Possible Solution
Suppress the error emitted here, or add additional detail to explain that the user can check by browsing to https://github.com/openfaas/faas-cli/releases/latest
faas-cli/commands/version.go
Line 71 in 7de6613
Context
Supporting a new user on Slack who on seeing the error thought they had encountered an error, effectively on step 1. By providing a more human message this false barrier to entry is removed.
Your Environment
faas-cli version
):docker version
):n/a
n/a
MacOS
n/a
The text was updated successfully, but these errors were encountered: