Closed asciiz closed 10 years ago
Hmm, that's weird. Looks like it is treating the directories as files.
Is the sync actually failing? Or is it just annoying to get all the warnings?
Drew
It is just annoying to get the warnings. I don't know if this has any side effects (sync works).
BTW, I noticed that stores are actually larger when zipped (350 bytes unzipped, 479 bytes zipped). I guess this is the zip compression overhead.
Today, I am getting a bunch of warnings and the sync fails (multiple errors):
[WARNING] DropboxSDK: error making request to /1/fileops/delete - (404) Path '/mainstore/baselines/22_44555e92-d174-4ec1-a7bc-61568f7ec8ae-8460-00002ea4bbc27167_9e1b3f00_1of2.cdeevent.cdezip' not found [WARNING] DropboxSDK: error making request to /1/fileops/delete - (404) Path '/mainstore/baselines/22_44555e92-d174-4ec1-a7bc-61568f7ec8ae-8460-00002ea4bbc27167_9e1b3f00_1of2.cdeevent' not found
Error Domain=CDEErrorDomain Code=102….and a list of "Domain=dropbox.com Code=404" errors.
I am not sure, but it seems that it happens if two clients accessing the Dropbox files at the same time.
It can be larger than your core data store. In version 1, it was 5-10 times larger. That's because it is not just storing your store, it is breaking it into transactions, which can be merged properly.
Unfortunately the warnings come from the Dropbox SDK itself. You could go in and comment out that log message.
Drew
On Jul 11, 2014, at 7:25, asciiz notifications@github.com wrote:
It is just annoying to get the warnings. I don't know if this has any side effects (sync works).
BTW, I noticed that stores are actually larger when zipped (350 bytes unzipped, 479 bytes zipped). I guess this is the zip compression overhead.
— Reply to this email directly or view it on GitHub.
The new error could be a bug, but it may also not be. Are you absolutely certain it is no longer syncing? Is it just slow to sync?
The error (102) is returned by mergeWithCompletion: and the sync fails. If I retry the sync later, it works.
Sync users networking, and you can expect failures for various reasons. As long as it works later, it should be no problem. An error isn't necessarily a big problem.
Drew
On 11 Jul 2014, at 12:30, asciiz notifications@github.com wrote:
The error (102) is returned by mergeWithCompletion: and the sync fails. If I retry the sync later, it works.
— Reply to this email directly or view it on GitHub.
I created other issues to improve this.
I am getting the following warnings (Ensembles v2, Dropbox 1.3.11):
[WARNING] DropboxSDK: error making request to /1/metadata/sandbox/MainStore.cdezip - (404) Path '/MainStore.cdezip' not found [WARNING] DropboxSDK: error making request to /1/metadata/sandbox/MainStore/stores.cdezip - (404) Path '/MainStore/stores.cdezip' not found [WARNING] DropboxSDK: error making request to /1/metadata/sandbox/MainStore/events.cdezip - (404) Path '/MainStore/events.cdezip' not found [WARNING] DropboxSDK: error making request to /1/metadata/sandbox/MainStore/baselines.cdezip - (404) Path '/MainStore/baselines.cdezip' not found [WARNING] DropboxSDK: error making request to /1/metadata/sandbox/MainStore/data.cdezip - (404) Path '/MainStore/data.cdezip' not found