CLI seems to handle network interrupt like 401

[pfeifferj]

observed behavior:

when a network connection is interrupted, the CLI throws errors as if the user was unauthorized

❯ ibmcloud ks cluster rm -c <example>
FAILED
Log in to the IBM Cloud CLI by running 'ibmcloud login'.

❯ ibmcloud login --apikey <redacted>
API endpoint: https://cloud.ibm.com
Region: us-south
Authenticating...
Post "https://iam.cloud.ibm.com/identity/token": EOF
                
API endpoint:   https://cloud.ibm.com
Region:         us-south
Not logged in.

Warning: unable to check latest CLI version.
TIP: use 'ibmcloud config --check-version=false' to disable update check.

FAILED
Unable to authenticate.

expected behavior:

A more precise and helpful error message pointing out network connectivity has been lost would be an improvement.

[steveclay]

The EOF is actually communicating the interrupt. That is the error that resulted which the CLI directly reports. The CLI then continues to try to check its own version, etc. which conceals this condition. Thanks for bringing this to our attention.