diff options
| author | kinuko@chromium.org <kinuko@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2013-03-25 18:24:10 +0000 |
|---|---|---|
| committer | kinuko@chromium.org <kinuko@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2013-03-25 18:24:10 +0000 |
| commit | 89c42ab7cf12cbc07af1fc0e0921527e3e8b323c (patch) | |
| tree | 2baebdd186c2a6d58f7901b4fe06513ed5911262 /remoting/host/local_input_monitor_unittest.cc | |
| parent | a54c078e2575f386a8427c8bcd6fb61fdebaf747 (diff) | |
| download | chromium_src-89c42ab7cf12cbc07af1fc0e0921527e3e8b323c.zip chromium_src-89c42ab7cf12cbc07af1fc0e0921527e3e8b323c.tar.gz chromium_src-89c42ab7cf12cbc07af1fc0e0921527e3e8b323c.tar.bz2 | |
SyncFS: Reset resource_id in metadata when remote directory is deleted
Based on tzik@'s patch: https://codereview.chromium.org/12983006/
(Patch set 1 is the original change)
- Resets sync_root_resource_id to empty when remote sync root folder is deleted
- Resets origin directory ID to empty when remote origin folder is deleted
- Runs EnsureOriginRootDirectory() in RegisterOrigin and ApplyLocalChange
- Handles not-found errors in LocalSync gracefully
BUG=177626
TEST=manual (see below)
NOTRY=true
1a. launch sample app, create some files, delete the origin folder on Drive (both a. while app is running, and b. after a restart while app is not running)
1b. do the same with 1a but delete the sync root directory on Drive.
2. confirm local files are also deleted by sync
3. add some more new files in the sample app
4. see if the remote origin folder is re-created and the new files are sync'ed
Review URL: https://chromiumcodereview.appspot.com/12967013
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@190443 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'remoting/host/local_input_monitor_unittest.cc')
0 files changed, 0 insertions, 0 deletions