You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am catching errors from hypercore.clear() method regularly. If the error message is to be trusted "No node found" could be a non-problem because clear() should be a node delete. I would like to create a test case to reproduce this, it involves replication between two hypercores involving a specific write pattern and could take awhile to pin down.
Additionally, supporting --limit involves replacing the default random-access-file storage provider with something that can partition data across multiple files, my fork of multi-random-access is a start towards this.
The text was updated successfully, but these errors were encountered:
rhodey
changed the title
--limit not supported
mirror --limit not supported
Nov 16, 2020
rhodey
changed the title
mirror --limit not supported
--limit not supported
Nov 19, 2020
I am catching errors from
hypercore.clear()
method regularly. If the error message is to be trusted "No node found" could be a non-problem becauseclear()
should be a node delete. I would like to create a test case to reproduce this, it involves replication between two hypercores involving a specific write pattern and could take awhile to pin down.radiowitness/lib/js/rw-peer/lib/ws-mirror.js
Line 77 in fde9f39
Additionally, supporting
--limit
involves replacing the default random-access-file storage provider with something that can partition data across multiple files, my fork of multi-random-access is a start towards this.The text was updated successfully, but these errors were encountered: