Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

--limit not supported #1

Open
rhodey opened this issue Nov 15, 2020 · 0 comments
Open

--limit not supported #1

rhodey opened this issue Nov 15, 2020 · 0 comments

Comments

@rhodey
Copy link
Owner

rhodey commented Nov 15, 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 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.

if (err && err.message === 'No node found') { // todo: hypercore bug!

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.

@rhodey rhodey changed the title --limit not supported mirror --limit not supported Nov 16, 2020
@rhodey rhodey changed the title mirror --limit not supported --limit not supported Nov 19, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant