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
{{ message }}
This repository has been archived by the owner on Mar 9, 2022. It is now read-only.
On the first pull sync of a remote database I see the total and completed increment as I would expect. Steadily increasing as the data comes in.
On a subsequent sync though it's a different story. The counts jump all over the place. Turning on debug stuff it appears that total is now tracking the number of documents queued for reading. So it's a value somwhere between 0 and 100. For example, instead of 0,100,250,345,487, etc I'm seeing 0,56,12,0,89,13,etc.
It also appears that when the replication stops, it's sending KVO notifications which zero out the completed field, before setting the mode to Stopped. So if I put up a dialog at the end, it's telling the user nothing was synced.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
On the first pull sync of a remote database I see the total and completed increment as I would expect. Steadily increasing as the data comes in.
On a subsequent sync though it's a different story. The counts jump all over the place. Turning on debug stuff it appears that total is now tracking the number of documents queued for reading. So it's a value somwhere between 0 and 100. For example, instead of 0,100,250,345,487, etc I'm seeing 0,56,12,0,89,13,etc.
It also appears that when the replication stops, it's sending KVO notifications which zero out the completed field, before setting the mode to Stopped. So if I put up a dialog at the end, it's telling the user nothing was synced.
The text was updated successfully, but these errors were encountered: