Closed EmiM closed 2 years ago
The issues that I encountered:
^ The above issues have been resolved:
IPFS.create
accepts PeerID's private key in init
options now)Agent
issue and released a new patch so I bumped IPFS js to 0.60.2 in wagglejest
setup file which sets global crypto. This may be a workaround.I noticed a change in replication behavior. This is what I see during test (1000 entries in log db):
replicate.progress
events (as before)replicate
event with big chunk of data
https://github.com/ZbayApp/waggle/runs/4326485402?check_suite_focus=trueAsked Orbit-db folks: https://gitter.im/orbitdb/Lobby?at=61a4d643cdb5c1081a3926d3
replicate
event works as expected (the previous chunky behavior was a bug):haad @haad:matrix.org [m] 16:07 hey, thanks for the pings. regarding the replicated event: 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.progress event 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.progress is fired, the DB index hasn't been updated yet with the replicated data.
Note: https://github.com/ZbayApp/waggle/pull/120 this may be helpful