delete/trash issue #3
Comments
update ... six hours later. Just FYI. |
... another update. The last "New file" is GONE again. Elapsed time: about 1 hour since deletion. So, it may be some caching - timing - synchronization issue after all. |
@seanpjanson, it's the sync scheduling latency problem. Maybe we should add a force synchronizer that runs immediately and doesn't wait for Android to schedule and perform the next sync. |
Yep, that's what I'm seeing. Do you want a narrated log of actions (last 6 On Wed, Jan 29, 2014 at 6:08 AM, Burcu Dogan notifications@github.comwrote:
|
It'd be helpful if you share your log on a gist, I can also investigate whether there is something else going wrong. |
It may not be an issue now, but since the latency is unpredictable and not On Wed, Jan 29, 2014 at 6:08 AM, Burcu Dogan notifications@github.comwrote:
|
You caught me, I have no clue how to use gist, actually how to tie gist to On Wed, Jan 29, 2014 at 6:16 AM, Burcu Dogan notifications@github.comwrote:
|
Yes, please add it as a comment here. |
the DEMO code has 2 little modifications,
Mostly confirms what you already know, the only 'surprise' 2:23 AM 1/29/2014 created 140129-022003 , list shows: 2:28 AM 1/29/2014 2:28 AM 1/29/2014 create file 2:30 AM 1/29/2014 delete 140129-022003 2:54 AM 1/29/2014 4:13 AM 1/29/2014 (elapsed 1:19) 4:53 AM 1/29/2014 6:07 AM 1/29/2014 As I said, probably nothing new. On Wed, Jan 29, 2014 at 6:31 AM, Burcu Dogan notifications@github.comwrote:
|
One last comment and I'll let you work. |
@seanpjanson, we're making some modifications to make the syncing more instantly. Btw, you can call |
Jun 2018 and still |
Hi, I am only bringing the SO discussions #21369573 and #21370636 here, so we do not vent it there. I installed this DEMO package and ran a few simple tests to see. The issue I mentioned on SO is showing with this DEMO as well. Steps to reproduce:
1/ Android device: "Create a file" ... creates "New file" in the root
2/ WEB browser: https://drive.google.com ... REMOVE (TRASH, DELETE...) the "New file"
3/ Android device: "List files with pagination" the list is unchanged, "New file" is showing.
Since this DEMO does not display the files' status, I ran the same (simplified) scenario in my test suite showing the file's "trashed" status, but did not get conclusive results.
Drive.DriveApi.query(mGAC, query).addResultCallback(new OnChildrenRetrievedCallback() {
@OverRide public void onChildrenRetrieved(MetadataBufferResult rslt) {
if (!rslt.getStatus().isSuccess()) return;
MetadataBuffer mdb = rslt.getMetadataBuffer();
for (int ii = 0; ii < mdb.getCount(); ii++) {
Log.i(TAG, (mdb.get(ii).isTrashed()?"-":"+")+mdb.get(ii).getTitle());
}
mdb.close();
}
});
Originally, the deleted file was showing as (+) (not trashed)
After I EMPTIED TRASH on the web, it changed status to (-) (trashed)
But when I re-ran the same test again (delete file, empty trash), I could not reproduce the same behavior. Conclusion: The trashed status (true/false, -/+) may be just random noise.
So, the behavior I would expect (after sync):
delete file on the web: The file/folder isTrashed() should change false -> true
recover file on the web: Change true -> false
empty trash - the file should not be listed anymore
This issue isn't a showstopper for me and I assume that it is just work-in-progress and it will be corrected eventually.
And the code Burcu's asking for is 0B1mQUW2aFJfdd2JTSkVIQnBoRm8.
The text was updated successfully, but these errors were encountered: