'replicate.progress' event is not always sent about orbit-db-store HOT 3 OPEN

Sorry I don't have a good idea of what is going on here. It's mostly good to hear this behavior is rare, as it's less of a blocker that way. The replicator needs to be rewritten in my opinion which I'm in the process of doing as part of orbitdb.

from orbit-db-store.

Well it's rare but it's not that rare. There are just a handful of us testing the orbitdb-based application and we've seen it several times already in our casual use of the app.

And "everyone converges to the same state" is the core feature of a CRDT, so if OrbitDB doesn't do this reliably and deterministically that's a big deal.

Are there any options beyond "wait for rewrite"? For example:

1. If this is a regression, can OrbitDB revert the change that brought it in?
2. Was it @haadcode that worked on the replicator refactor? Would they have any ideas of what might be going wrong?
3. Can we invest in some testing infrastructure around this so that, at the very least, when the rewrite is ready we can be confident that the problem is no longer happening? This seems like the most important thing.

Also, when should we expect the work you're doing to be ready?

from orbit-db-store.

You could try using 0.27 for the time being and see if the behavior is still there. It's possible this isn't related to changes in #933

from orbit-db-store.