Chromium Code Reviews
chromiumcodereview-hr@appspot.gserviceaccount.com (chromiumcodereview-hr) | Please choose your nickname with Settings | Help | Chromium Project | Gerrit Changes | Sign out
(95)

Issue 14838003: Try fast-fetch rather than full fetch if drive::FileSystem::GetEntryInfo failed. (Closed)

Created:
7 years, 7 months ago by kinaba
Modified:
7 years, 7 months ago
Reviewers:
hashimoto, satorux1
CC:
chromium-reviews, tfarina, oshima+watch_chromium.org, stevenjb+watch_chromium.org, nkostylev+watch_chromium.org, davemoore+watch_chromium.org
Visibility:
Public.

Description

Try fast-fetch rather than full fetch if drive::FileSystem::GetEntryInfo failed. GetEntryInfoByPath is not only used for querying an entry info, but also for just testing the existence of an entry. So, it is not always desirable to start full fetch when it does not exist locally. The new implementation falls back to full fetch after all when the parent directory's entry is not ready either. This should not be an issue, however. Existence testing most typically happens when user tries to put a new file in a folder, in which case, the folder is already opened in UI and hence loaded. BUG=236708 TEST=the steps explained in BUG. R=satorux@chromium.org Committed: https://src.chromium.org/viewvc/chrome?view=rev&revision=198671

Patch Set 1 #

Total comments: 2

Patch Set 2 : Added (and fixed) tests. #

Total comments: 5

Patch Set 3 : rebase #

Patch Set 4 : Fix comments and function name #

Patch Set 5 : rebase #

Unified diffs Side-by-side diffs Delta from patch set Stats (+108 lines, -52 lines) Patch
M chrome/browser/chromeos/drive/file_system.h View 1 2 1 chunk +11 lines, -7 lines 0 comments Download
M chrome/browser/chromeos/drive/file_system.cc View 1 2 3 chunks +28 lines, -25 lines 0 comments Download
M chrome/browser/chromeos/drive/file_system_unittest.cc View 1 2 3 8 chunks +69 lines, -20 lines 0 comments Download

Messages

Total messages: 10 (0 generated)
kinaba
7 years, 7 months ago (2013-05-02 04:26:12 UTC) #1
satorux1
looks like a great change. would it be possible to write a test? https://codereview.chromium.org/14838003/diff/1/chrome/browser/chromeos/drive/file_system.cc File ...
7 years, 7 months ago (2013-05-02 04:42:38 UTC) #2
kinaba
On 2013/05/02 04:42:38, satorux1 wrote: > looks like a great change. would it be possible ...
7 years, 7 months ago (2013-05-02 06:21:28 UTC) #3
kinaba
On 2013/05/02 06:21:28, kinaba wrote: > On 2013/05/02 04:42:38, satorux1 wrote: > > looks like ...
7 years, 7 months ago (2013-05-02 08:35:54 UTC) #4
kinaba
Added tests for the new flow, and fixed failure in existing tests. (Sorry I contaminated ...
7 years, 7 months ago (2013-05-02 11:31:34 UTC) #5
kinaba
https://codereview.chromium.org/14838003/diff/1/chrome/browser/chromeos/drive/file_system.cc File chrome/browser/chromeos/drive/file_system.cc (right): https://codereview.chromium.org/14838003/diff/1/chrome/browser/chromeos/drive/file_system.cc#newcode750 chrome/browser/chromeos/drive/file_system.cc:750: // If we don't know about the directory, start ...
7 years, 7 months ago (2013-05-02 11:32:11 UTC) #6
satorux1
LGTM with nits. hashimoto@, could you land this patch on behalf of kinaba who'll be ...
7 years, 7 months ago (2013-05-07 06:29:45 UTC) #7
hashimoto
Uploading a new patch https://codereview.chromium.org/14838003/diff/14001/chrome/browser/chromeos/drive/file_system_unittest.cc File chrome/browser/chromeos/drive/file_system_unittest.cc (right): https://codereview.chromium.org/14838003/diff/14001/chrome/browser/chromeos/drive/file_system_unittest.cc#newcode311 chrome/browser/chromeos/drive/file_system_unittest.cc:311: bool SaveTestFileSystem(SaveTestFileSystemParam param) { On ...
7 years, 7 months ago (2013-05-07 06:49:01 UTC) #8
kinaba
lgtm
7 years, 7 months ago (2013-05-07 06:52:34 UTC) #9
hashimoto
7 years, 7 months ago (2013-05-07 08:28:10 UTC) #10
Message was sent while issue was closed.
Committed patchset #5 manually as r198671 (presubmit successful).

Powered by Google App Engine
This is Rietveld 408576698