You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hitting MS Office document "save" button several times during a short period of time could cause an infinite sync loop.
Steps to reproduce:
Start 2x megacli application, sync two local folders to the same remote folder.
Start MS Office, create a document, save it in the local synced folder.
Wait for a full sync in both megacli.
Now type something quickly and press "CTRL +S" to save the changes.
Repeat previous step 4-5 times.
both megacli get into infinite sync loop.
Sending:
2 files added or updated
1 user received or updated
Sync - state change of node test.docx to Syncing
Sync - state change of node to Syncing
Sync - state change of node test.docx to Synced
Sync - state change of node to Synced
Sync - state change of node test.docx to Pending
Sync - state change of node to Pending
Sync - creating remote file test.docx by copying existing remote file
Sync - state change of node test.docx to Syncing
Sync - state change of node to Syncing
POST target URL: https://g.api.mega.co.nz/cs?id=nldxyghcjb&sid=y6kHA6CM5mAz7Bn4vhhH8nN3TmpUZmQ0Nld
Sending: [{"a":"p","i":"hbmnohybow","t":"5VcRmRiT","n":[{"h":"lZtViBRJ","t":0,"a":"3eoKLmTAkSblRG-
hvuCZxAIAz01drvYyQE","ts":1400965249}]},{"a":"m","i":"hbmnohybow","n":"IdMxRYKA","t":"JRkmyBKJ"}]
MEGA> Received: [{"f":[{"h":"wRdnxBAA","t":0,"a":"3eoKLmTAkSblRG-Xk5mpUrltuExonDzB6VnUsfyNqeZ5zhQG
"ts":1400965249,"p":"5VcRmRiT","u":"swNjTfd46WQ","s":11262}]},0]
Sync - state change of node test.docx to Synced
Sync - state change of node to Synced
2 files added or updated
MEGA> Received: {"a":[{"a":"t","i":"hbmnohybow","t":{"f":[{"h":"wRdnxBAA","t":0,"a":"3eoKLmTAkSblR
580ryU2oJXtu4uhvuCZxAIAz01drvYyQE","ts":1400965249,"p":"5VcRmRiT","u":"swNjTfd46WQ","s":11262}]},"
ow","t":{"f":[{"h":"IdMxRYKA","p":"JRkmyBKJ","u":"swNjTfd46WQ","t":0,"a":"ssSqO-Xs6ldJTBYLnSDWwxmq
ZvtUYw7LUOlomZmhByYyfU","s":11412,"ts":1400965729,"tdm":-447}],"u":[{"u":"swNjTfd46WQ","m":"spoh21
O-Xs6ldJTBYLnSDWwxmqtZNSUqUeflbOg3p5hl7hDLxLhKEuhd0OcSTCrwFaI6WEKQiyUSu4szL7Ete19Q","k":"swNjTfd46
1412}]},"ou":"swNjTfd46WQ"},{"a":"d","i":"dgvgahiblt","n":"wRdnxBAA","ou":"swNjTfd46WQ"},{"a":"t",
Xk5mpUrltuExonDzB6VnUsfyNqeZ5zhQGKuxm8nPAkf7k23-n4_UbK2RZ83fgv7x8TvpSEg","k":"swNjTfd46WQ:64rw2rZ3
":"spoh21@gmail.com"}]},"ou":"swNjTfd46WQ"}],"sn":"yKmp_K_FTiw"}
POST target URL: https://g.api.mega.co.nz/sc?sn=yKmp_K_FTiw&sid=y6kHA6CM5mAz7Bn4vhhH8nN3TmpUZmQ0Nl
Sending:
2 files added or updated
1 user received or updated
Sync - state change of node test.docx to Syncing
Sync - state change of node to Syncing
Sync - state change of node test.docx to Synced
Sync - state change of node to Synced
Sync - state change of node test.docx to Pending
Sync - state change of node to Pending
Sync - creating remote file test.docx by copying existing remote file
Sync - state change of node test.docx to Syncing
Sync - state change of node to Syncing
POST target URL: https://g.api.mega.co.nz/cs?id=nldxyghcjc&sid=y6kHA6CM5mAz7Bn4vhhH8nN3TmpUZmQ0Nld
Sending: [{"a":"p","i":"hbmnohybow","t":"5VcRmRiT","n":[{"h":"lZtViBRJ","t":0,"a":"3eoKLmTAkSblRG-
hvuCZxAIAz01drvYyQE","ts":1400965249}]},{"a":"m","i":"hbmnohybow","n":"cNcGCJYA","t":"JRkmyBKJ"}]
MEGA> Received: [{"f":[{"h":"lRcS2RjQ","t":0,"a":"3eoKLmTAkSblRG-Xk5mpUrltuExonDzB6VnUsfyNqeZ5zhQG
"ts":1400965249,"p":"5VcRmRiT","u":"swNjTfd46WQ","s":11262}]},0]
Sync - state change of node test.docx to Synced
Sync - state change of node to Synced
As well reproduced issue #26 (haven't seen this issue on Windows for a long time!). Remote folder had 4x test.docs files.
The text was updated successfully, but these errors were encountered:
Hitting MS Office document "save" button several times during a short period of time could cause an infinite sync loop.
Steps to reproduce:
As well reproduced issue #26 (haven't seen this issue on Windows for a long time!). Remote folder had 4x test.docs files.
The text was updated successfully, but these errors were encountered: