-
-
Notifications
You must be signed in to change notification settings - Fork 3k
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
ipfs init is not reporting failures #1130
Labels
exp/novice
Someone with a little familiarity can pick up
kind/bug
A bug in existing code (including security flaws)
topic/commands
Topic commands
topic/daemon + init
Comments
whyrusleeping
added
kind/bug
A bug in existing code (including security flaws)
topic/commands
Topic commands
topic/daemon + init
labels
Apr 24, 2015
Good catch, should be a moderately easy fix in |
woahhh interesting. we should add a test case for this to sharness tests. |
This was referenced May 20, 2015
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
exp/novice
Someone with a little familiarity can pick up
kind/bug
A bug in existing code (including security flaws)
topic/commands
Topic commands
topic/daemon + init
Given the
$IPFS_PATH
is not writable foripfs init
the command does show the output we're used to as if it worked fine. Instead it should show an fatal error becauseipfs init
is in fact not able to write into that directory and it is empty afterwards which causes strange errors:The text was updated successfully, but these errors were encountered: