Checkpoint iteration strategy failing in simultaneous pull-push scenario.

[utkarshtopinkatti051]

Have you found a bug?

Yes! The checkpoint iteration strategy uses the "updatedAt" field of the latest pulled document, but in this case, the collection doesn't have this document. It's strange that this record is not logged in the conflict resolver either. Here are the steps to reproduce the issue:

1. A document was updated on the server side while the client was in offline mode.
2. The client updated the document while offline.
3. The client came back online.
4. The pull query was executed first, followed by the push query.
5. The checkpoint iteration used the "updatedAt" field of the latest pulled document, but the collection still had the older document instead of the latest pulled document.

References

I further checked previously raised issue around this area but not sure if this is related to the one, I am facing.
#5571 (comment)

Rxdb Version used

-v15.16.0

[pubkey]

Please make a PR with a test case, then I can fix that otherwise I cannot start working on it.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed soon. If you still have a problem, make a PR with a test case or to prove that you have tried to fix the problem. Notice that only bugs in the rxdb premium plugins are ensured to be fixed by the maintainer. Everything else is expected to be fixed by the community, likely you must fix it by yourself.

[pubkey]

@utkarshtopinkatti051 I am still interested in this. Can you make a PR with a failing test case to reproduce the problem?