Not parsing HTTPS_PROXY properly

[GreenStage]

Describe the bug
All kubectl commands fail with : getaddrinfo ENOTFOUND socks5 when running KUI with the HTTPS_PROXY env set to socks5://127.0.0.1:6783,

Steps to reproduce the behavior

1. Open windows Command Prompt
2. Run SET HTTPS_PROXY=socks5://127.0.0.1:6783 && START Kui
3. kubectl get pods -n <namespace>
4. See error

Expected behavior
kubectl requests should go through the HTTPS_PROXY smoothly

Screenshots

System

• Kui version: 11.5.0
• Operating system: Windows x64

[starpit]

thanks for the bug report! we'll check it out.

[starpit]

Sorry it took so long to get to this one. The fix will be included in the next release!

[starpit]

The fix has been released in 12.0.0. If the problem persists, ping here!

[drennalls]

I'm still seeing the same thing on 13.0.0 (on Linux)