Overview
OrbitDB errors that should be expected (e.g. failure to get a block from storage that you don't have) can result in crashes as they cascade through Helia and Libp2p (this often shows up as the "Want was aborted" errors). This is a result of how OrbitDB handles (or in many cases doesn't handle) errors, particularly during syncs.
Acceptance Criteria
- Better handle errors in OrbitDB so they still produce the intended behavior without crashing Quiet
- Update submodule in Quiet
- Ensure tests in Quiet and OrbitDB pass
Overview
OrbitDB errors that should be expected (e.g. failure to get a block from storage that you don't have) can result in crashes as they cascade through Helia and Libp2p (this often shows up as the "Want was aborted" errors). This is a result of how OrbitDB handles (or in many cases doesn't handle) errors, particularly during syncs.
Acceptance Criteria