Skip to content

--limit not supported #1

@rhodey

Description

@rhodey

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.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions