File sync can only partially restart after waking from sleep

[noizwaves]

What happened?

Several of our users have reported random instances of files not syncing from their laptops to remote pods. This seems to happen after they've left devspace dev running whilst putting their laptop to sleep. We utilize a VPN to connect to Loft, and while the laptop is sleeping, the VPN switches off.

When woken up, devspace dev is able to restore some file syncs, but sometimes not all of them, and this leads to a confusing experience.

We captured (and sanitized) the output of devspace dev here: devspace_logs.txt

What did you expect to happen instead?

Ideally, all of the file sync should be restarted when the laptop wakes up and the VPN is connected. Alternatively, devspace dev could just terminate, alerting the developer they need to run the command again.

How can we reproduce the bug? (as minimally and precisely as possible)

1. Configure a project with devspace that uses multiple file synchronizations
2. Run devspace dev
3. Put computer to sleep for ~4 hours
4. Wake up computer
5. Change some files
6. Check to see if the changes were replicated to all pods as expected

Local Environment:

• DevSpace Version: devspace version 5.12.2
• Operating System: mac
• Deployment method: helm

Kubernetes Cluster:

• Cloud Provider: aws
• Kubernetes Version:

Client Version: version.Info{Major:"1", Minor:"21", GitVersion:"v1.21.0", GitCommit:"cb303e613a121a29364f75cc67d3d580833a7479", GitTreeState:"clean", BuildDate:"2021-04-08T21:15:16Z", GoVersion:"go1.16.3", Compiler:"gc", Platform:"darwin/amd64"}
Server Version: version.Info{Major:"1", Minor:"17+", GitVersion:"v1.17.12-eks-7684af", GitCommit:"7684af4ac41370dd109ac13817023cb8063e3d45", GitTreeState:"clean", BuildDate:"2020-10-20T22:57:40Z", GoVersion:"go1.13.15", Compiler:"gc", Platform:"linux/amd64"}

Anything else we need to know?
We are running the Cisco AnyConnect VPN client.

/kind bug

[FabianKramm]

@noizwaves thanks for reporting this issue and the logs, they help a lot! We'll try to reproduce this and fix it. I think I already know what the problem could be.

[noizwaves]

Great, thanks @FabianKramm! I forgot to mention, this is not a high priority for us. It's only affected a handful of users, and the workaround of restarting devspace dev is pretty easy to do.