Hello, unfortunately I (still) have the replication problem after upgrading orbit-db to 0.28.0. I have a simple test that reproduces it (one node adding entries to the log db, other node connecting and waiting for replication). I can see that they are indeed connecting (orbitdb logs and libp2p events show that), I can also see that heads have been exchanged, however the second db does not receive any replication events, the db is empty.
2021-11-22T21:53:58.577Z [DEBUG] orbit-db: New peer 'QmUZCtB3p9RPjLfk9LdCYc7bdAmVtzg5Tw9YeiNYYqM4VB' connected to '/orbitdb/zdpuB3VCfydEyPvH8ftmokhK19HW1LHmxAPLM8dAje2caFGMB/092183012' 2021-11-22T21:53:58.578Z [DEBUG] exchange-heads: Create a channel to QmUZCtB3p9RPjLfk9LdCYc7bdAmVtzg5Tw9YeiNYYqM4VB 2021-11-22T21:53:58.579Z [DEBUG] exchange-heads: Channel created to QmUZCtB3p9RPjLfk9LdCYc7bdAmVtzg5Tw9YeiNYYqM4VB 2021-11-22T21:53:58.587Z [DEBUG] pubsub: Peer joined /orbitdb/zdpuAvDtJxmX2PxFFvmGAZTj1QoDvThQgZ64LfSGtWox1qW2J/3479623913-test:
Usually I would assume that the problem is on our side but we have been running this test for a while now and it has been passing.
My changes are here: ZbayApp/waggle#152, the test can be run locally
DEBUG='libp2p:websockets:listener:waggle*,waggle:*' ts-node src/nodeTest/testReplicate.ts --nodesCount 1 --timeThreshold 200 --entriesCount 20 --useTor
Maybe I am missing something obvious, If you had time to look at this I would really appreciate. We can also DM to not spam here.
Hello, I am building a react app working with orbit-db. I am having this error
is not supported by the IPLD Data Model and cannot be encoded
I initialize IPFS like this https://github.com/ipfs-shipyard/ipfs-share-files/blob/2d3aecdbc694e41d3151e09526865eb5c88334cb/src/bundles/ipfs-provider.js#L44 with the latest version of
ipfs-provider, ipfs-http-client and ipfs-core
"ipfs-http-client": "^54.0.1", "ipfs-provider": "^2.1.0", "ipfs-core": "0.12.2" "orbit-db": "^0.28.0", "orbit-db-store": "^4.3.2",
Any idea? thank you in advance
Hello, I have two issues:
1) We just switched to new orbit-db and I noticed that the behaviour of
replicated event changed.
I have a simple test - one node adds 1000 entries to its local log db, second node connects and replicates this db.
Previously (orbit-db < 0.27) I was receiving
replicated event every ~32 entries (smaller chunks).
Now I get only one big chunk and one
replicated event after all 1000 entries are done being replicated.
Is it an expected behaviour? Is there a way to send smaller chunks as before?
2) What times of replication I should expect after upgrading orbit-db, ipfs etc.?
Currently we experience ~20 seconds for localhost p2p network and ~150 seconds for tor network:
https://github.com/ZbayApp/waggle/runs/4326485402?check_suite_focus=true (both 1000 entries).
The times are very similar to what was before:
replicatedevent: indeed, this is now sent only when the db has been (fully) replicated. in fact, the previous behaviour wasn't intended (replicated events "chunked"). however, if I understand the need described above, you want to be able to "know when some progress of replication has been made" and the
replicate.progressevent will give you that (see https://github.com/orbitdb/orbit-db-store/blob/main/src/Store.js#L100 for the callback signature and params). it's emitted for each replicated db log entry. with that, you can eg. show a nice progress bar, or hook to it to show the replicated data to the user. note though that when
replicate.progressis fired, the DB index hasn't been updated yet with the replicated data.