-
Notifications
You must be signed in to change notification settings - Fork 63
Closed
Labels
P1High: Likely tackled by core team if no one steps upHigh: Likely tackled by core team if no one steps upexp/expertHaving worked on the specific codebase is importantHaving worked on the specific codebase is importanthelp wantedSeeking public contribution on this issueSeeking public contribution on this issuekind/bugA bug in existing code (including security flaws)A bug in existing code (including security flaws)
Description
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:
js-ipfsd-ctl/test/spawn-options.spec.js
Line 121 in 151303c
// `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
dryajov
Metadata
Metadata
Assignees
Labels
P1High: Likely tackled by core team if no one steps upHigh: Likely tackled by core team if no one steps upexp/expertHaving worked on the specific codebase is importantHaving worked on the specific codebase is importanthelp wantedSeeking public contribution on this issueSeeking public contribution on this issuekind/bugA bug in existing code (including security flaws)A bug in existing code (including security flaws)