Fix incremental sync behavior of DriveFileSyncService.

Fix incremental sync behavior of DriveFileSyncService.

This change contains:
 - check the presence of the metadata entry before delete it,
 - +1 for start of changestamp to fetch to prevent fetching a change multiple times.

BUG=156041
Committed: https://src.chromium.org/viewvc/chrome?view=rev&revision=170934

[tzik, 2012-12-04 08:35:48]

PTAL

[kinuko, 2012-12-04 08:55:42]

lgtm mod 1 nit

https://codereview.chromium.org/11418305/diff/1/chrome/browser/sync_file_syst...
File chrome/browser/sync_file_system/drive_file_sync_service.cc (right):

https://codereview.chromium.org/11418305/diff/1/chrome/browser/sync_file_syst...
chrome/browser/sync_file_system/drive_file_sync_service.cc:1087:
CompleteRemoteSync(param.Pass(), fileapi::SYNC_STATUS_OK);
Could this happen? (We're in metadata.conflicted() block)

[tzik, 2012-12-04 09:14:28]

Thanks!

https://codereview.chromium.org/11418305/diff/1/chrome/browser/sync_file_syst...
File chrome/browser/sync_file_system/drive_file_sync_service.cc (right):

https://codereview.chromium.org/11418305/diff/1/chrome/browser/sync_file_syst...
chrome/browser/sync_file_system/drive_file_sync_service.cc:1087:
CompleteRemoteSync(param.Pass(), fileapi::SYNC_STATUS_OK);
On 2012/12/04 08:55:42, kinuko wrote:
> Could this happen? (We're in metadata.conflicted() block)

Done. It can't be reached.

[commit-bot: I haz the power, 2012-12-04 09:14:53]

CQ is trying da patch. Follow status at
https://chromium-status.appspot.com/cq/tzik@chromium.org/11418305/4001

[commit-bot: I haz the power, 2012-12-04 11:57:46]

Change committed as 170934