More than one manual sync can be executed at one time

[Manuel de la Peña]

The application allow to perform more than one u1sync at a time. This should be avoided.

[John A Meinel (jameinel)]

I think this bug is still not fixed.

I went to the client and saw it saying "Idle", which I think was incorrect. I then asked it to Synchronize Now, and I believe it is executing 2 syncs. At least, I assume the ".97fe96f2-d96e-4f3d-8383-2620595d159f" file is indicative of an ongoing sync, and there are currently 2 of those files active at the same time.

[John A Meinel (jameinel)]

As a guess, the client uses the "State" indicator to tell if it can start a sync or not. And since the state was incorrect, it allowed me to launch a new one. I did check again, and I couldn't start a 3rd Sync.

I wonder if it is because the client crashed and I restarted it. And it didn't determine that it was already Synching. Maybe it needs a way to poll-on-startup the current state?

[Manuel de la Peña (mandel)]

Bingo, you just pointed out the issue. The sync will not stop until you exit the sync operation is done (to keep the state). Because the client crashed the sync process was left running so that you machine was not in an intermediate state. When you launched the app, the state was wrong.

I think it is safe to create a diff bug for this in which we state the exact way to reproduce it, do you want me to take care of that?