Port forwarding stops when PC goes idle but still shows as Active on Windows

[ImRodry]

Describe the bug Title says it all, if you have an active Port Forwarding and your PC goes to sleep, when you restart it, Lens will connect back to the containers and show the previously active port forwardings as still being active, despite them nor working and needing to be stopped and restarted

To Reproduce Steps to reproduce the behavior:

1. Open Lens and connect to a cluster
2. Go to Network - Port Forwarding and make sure at least one is active
3. Put your PC to sleep and wait 1-2 minutes. This can also be triggered by letting the PC idle for a long time and automatically hibernate
4. Wake the PC back up
5. Check the Port Forwarding tab - see that all items that were active previously remain active
6. Try to access one of them and observe that it's unreachable

Expected behavior Lens should attempt to restart the port forwarding or at least not display it as active

Environment (please complete the following information):

• Lens Version: 2022.12.221341-latest
• OS: Windows 11
• Installation method (e.g. snap or AppImage in Linux): Why the hell would I remember that

Logs: When you run the application executable from command line you will see some logging output. Please paste them here: Not sure what you mean

Kubeconfig: Quite often the problems are caused by malformed kubeconfig which the application tries to load. Please share your kubeconfig, remember to remove any secret and sensitive information. I don't think this is a kubeconfig issue and I cannot share mine

[quassy]

I can confirm the same issue exists on macOS Ventura 13.3.1 with Lens version 2023.4.141316-latest.

[richard-fairthorne]

Can confirm macOS Sonoma 14.0 on Apple Silicon M1 with lens 2023.9.290703-latest

Problem has persisted since I started using Lens, probably a year or so ago.