Jim Ehrismann

@pwurbs is this still a problem on Lens 5.4.3?

@pwurbs is the cluster local (from a local kubeconfig) or a cluster shared through Lens Spaces? Is it EKS, or GKE, or...? Is your corporate proxy set up such that...

ah, right. But if that's all it is then I think @pwurbs could at least test via starting Lens in a terminal like: ``` HTTPS_PROXY="http://:" /Applications/Lens.app/Contents/MacOS/Lens ```

> ``` > ←[32minfo←[39m: ←[32m←[2mÔû¬←[22m←[0m ←[0mCreating a new port-forward doaas-dev1/service/jenkins:8080←[3m←[2m +10s←[22m←[23m > ←[33mwarn←[39m: ←[33m←[2mÔû¬←[22m←[0m ←[0m[getPortFrom]: failed to retrieve port via /^forwarding from (?.+) ->/i: ←[3m←[2m +19s←[22m←[23m > ←[31merror←[39m: ←[31m←[2mÔöÅ←[22m←[0m ←[0m[PORT-FORWARD-ROUTE]:...

Or maybe this will help: https://github.com/lensapp/lens/issues/2088#issuecomment-773846996

The hardest part for me is reproducing the issue. I've set up a proxy server, and limited network access to only the proxy. Do you have details on your proxy...

@pwurbs, I managed to configure a proxy plus firewall rules such that I can reproduce the problem. I was also able to reproduce and fix the helm issue. Unfortunately applying...

The helm fix should be in 5.4.7 Shell in a pod or node can be opened from the context menu for a given pod or node on the listing page:...

Ah, looks like you're living with another bug, there are possible causes/solutions here: https://github.com/lensapp/lens/issues/3548 Did you add any extensions that didn't install properly? Lens uses npm to install extensions, if...

This looks rather big for a patch release...