kryond

Alright, the second solution may not be that complex. Since the query has a record of latestChangesEvent, the solution is quite straightforward. We just need to record a checkpoint before...

> Hi [@kryon-7](https://github.com/kryon-7) Thank you for the investigation. Do you think it is possible to craft a unit test that fails nearly 100% to reproduce this? I think we have...

We can make the server wait 2 seconds after finishing the query (to fake processing time) before sending results back. During this wait, the client can send lots of insert/delete/update...

Extending query execution time may trigger collection creation limits. Perhaps we should configure the test cases to run sequentially rather than in parallel. Alternatively, we could create a dedicated randomDelayStorage...

> Hi [@kryon-7](https://github.com/kryon-7) Thank you for the investigation. Do you think it is possible to craft a unit test that fails nearly 100% to reproduce this? I think we have...

Hi @pubkey ,I understood. I attempt to reproduce the issue by inserting a large number of documents while simultaneously executing queries with multiple sort fields. However, I've observed that the...

Hello! @pubkey I've just been thinking. It's really hard to encounter this error when using the real storage, because the test environment is too ideal, including the network and so...

bt remote storage is another process,so it can be reproduced in mongodb [ci result](https://github.com/kryon-7/rxdb/actions/runs/14491815741)

Actually, this issue isn't limited to MongoDB—it can happen with any remote storage. I tried running the remote server in a separate process instead of sharing one with the client,...

Hi @pubkey. I've submitted a PR #7075 to reproduce this bug, but the test case requires at least 6 seconds to complete. However, some test scripts have a timeout setting...