mirrors/zotero
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages 1 Wiki Activity Actions

Fix out-of-memory error syncing collections nested inside each other

Browse source 
It shouldn't be possible for collections to be nested this way, if it
happens, it shouldn't result in an infinite loop.

This removes one of the parent assignments at sync time.
This commit is contained in:
Dan Stillman 2019-11-26 15:30:43 -07:00
parent 47d8a54600
commit 8c7677a009
4 changed files with 57 additions and 1 deletions
Download patch file Download diff file Expand all files Collapse all files

27
test/tests/syncLocalTest.js
View file

@ -466,6 +466,33 @@ describe("Zotero.Sync.Data.Local", function() {
})
describe("#getUnsynced()", function () {
it("should correct incorrectly nested collections", async function () {
var c1 = await createDataObject('collection');
var c2 = await createDataObject('collection');
c1.parentID = c2.id;
await c1.saveTx();
await Zotero.DB.queryAsync(
"UPDATE collections SET parentCollectionID=? WHERE collectionID=?",
[
c1.id,
c2.id
]
);
await c2.reload(['primaryData'], true);
var ids = await Zotero.Sync.Data.Local.getUnsynced('collection', Zotero.Libraries.userLibraryID);
// One of the items should still be the parent of the other, though which one is undefined
assert.isTrue(
(c1.parentID == c2.id && !c2.parentID) || (c2.parentID == c1.id && !c1.parentID)
);
});
});
describe("#processObjectsFromJSON()", function () {
var types = Zotero.DataObjectUtilities.getTypes();