Skip to content

In proc nodes can not be spawned on top of existing repos #214

@JonKrone

Description

@JonKrone

In-process js-ipfs instances are not aware of whether or not they have spawned on top of an existing repo. This basically breaks the node as it can neither .start or .init.

I believe this is the cause of an error mentioned in a TODO here:

// `Error: Not able to start from state: uninitalized`

I think a fix for this can largely mirror how a js-ipfs instance works if the repo exists.

Another in-proc node issue that might be good to group with this: #208

Metadata

Metadata

Assignees

No one assigned

    Labels

    P1High: Likely tackled by core team if no one steps upexp/expertHaving worked on the specific codebase is importanthelp wantedSeeking public contribution on this issuekind/bugA bug in existing code (including security flaws)

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions