www

Unnamed repository; edit this file 'description' to name the repository.
Log | Files | Refs | Submodules | README | LICENSE

commit bfbac246675f920764be6d1d8cb86cc30bb19afc
parent 7dce0694901f6a687dc5d9ecf9248195fc8dfdfb
Author: Dan Stillman <dstillman@zotero.org>
Date:   Wed,  6 Jul 2016 13:54:25 -0400

Condense debug output for skipped up-to-date items when syncing

Diffstat:
Mchrome/content/zotero/xpcom/sync/syncEngine.js | 7++++++-
1 file changed, 6 insertions(+), 1 deletion(-)

diff --git a/chrome/content/zotero/xpcom/sync/syncEngine.js b/chrome/content/zotero/xpcom/sync/syncEngine.js @@ -371,17 +371,22 @@ Zotero.Sync.Data.Engine.prototype._downloadUpdatedObjects = Zotero.Promise.corou let versions = yield objectsClass.getObjectVersions( this.libraryID, Object.keys(results.versions) ); + let upToDate = []; for (let key in results.versions) { // Skip objects that are already up-to-date. Generally all returned objects should have // newer version numbers, but there are some situations, such as full syncs or // interrupted syncs, where we may get versions for objects that are already up-to-date // locally. if (versions[key] == results.versions[key]) { - Zotero.debug("Skipping up-to-date " + objectType + " " + this.libraryID + "/" + key); + upToDate.push(key); continue; } keys.push(key); } + if (upToDate.length) { + Zotero.debug(`Skipping up-to-date ${objectTypePlural} in library ${this.libraryID}: ` + + upToDate.sort().join(", ")); + } // In child-items mode, remove top-level items that just failed if (objectType == 'item' && !options.top && this.failedItems.length) {