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
error: current-context must exist in order to minify
[rsrchboy:~/.vim] [⎈] master(+76/-7,2)+* 20s ± echo $ZSH_VERSION
5.8
error: current-context must exist in order to minify
[rsrchboy:~/.vim] [⎈] master(+76/-7,2)+* 127 ± uname -a
Linux zeus 5.14.8-arch1-1 #1 SMP PREEMPT Sun, 26 Sep 2021 19:36:15 +0000 x86_64 GNU/Linux
error: current-context must exist in order to minify
[rsrchboy:~/.vim] [⎈] master(+76/-7,2)+* 1 ± cat /etc/os-release
NAME="Arch Linux"
PRETTY_NAME="Arch Linux"
ID=arch
BUILD_ID=rolling
ANSI_COLOR="38;2;23;147;209"
HOME_URL="https://archlinux.org/"
DOCUMENTATION_URL="https://wiki.archlinux.org/"
SUPPORT_URL="https://bbs.archlinux.org/"
BUG_REPORT_URL="https://bugs.archlinux.org/"
LOGO=archlinux
error: current-context must exist in order to minify
[rsrchboy:~/.vim] [⎈] master(+76/-7,2)+* ±
Set LP_ENABLE_KUBECONTEXT=1 and LP_ENABLE_KUBE_NAMESPACE=1
Don't have any k8s contexts available; e.g. all minikube environments destroyed
Behold, leaked error messages from kubectl
Expected Behavior
As with other bits of liquidprompt, I'd expect the k8s portion of the prompt to simply not be present when no contexts are configured.
Current Behavior
error: current-context must exist in order to minify
[rsrchboy:~/.vim] [⎈] master(+76/-7,2)+* ±
Note the error, and that the k8s section of the prompt is still present.
Possible Solution
It would be easy to mask the error message, e.g. add 2>/dev/null to the relevant command. However, this would still leave the part of the prompt present.
The text was updated successfully, but these errors were encountered:
Shell, OS information:
kubectl version:
Liquidprompt version: 9d27a43
Steps to Reproduce
LP_ENABLE_KUBECONTEXT=1
andLP_ENABLE_KUBE_NAMESPACE=1
Expected Behavior
As with other bits of liquidprompt, I'd expect the k8s portion of the prompt to simply not be present when no contexts are configured.
Current Behavior
Note the error, and that the k8s section of the prompt is still present.
Possible Solution
It would be easy to mask the error message, e.g. add
2>/dev/null
to the relevant command. However, this would still leave the part of the prompt present.The text was updated successfully, but these errors were encountered: