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.

Sign up for GitHub

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

Jump to bottom

ipfs cat <hash> needs a good error message #1060

Closed
jbenet opened this issue Apr 12, 2015 · 3 comments
Closed

ipfs cat <hash> needs a good error message #1060

jbenet opened this issue Apr 12, 2015 · 3 comments
Labels
kind/bug A bug in existing code (including security flaws) topic/cleanup Topic cleanup topic/commands Topic commands

Comments

@jbenet
Copy link
Member

jbenet commented Apr 12, 2015 

> ipfs cat Qmaa4Rw81a3a1VEx4LxB7HADUAXvZFhCoRdBzsMZyZmqHD
Error: Lock Create of foo/daemon.lock (abs: /Users/jbenet/.go-ipfs) failed: open .go-ipfs/daemon.lock: no such file or directory

unhelpful error message. should be:

> ipfs cat Qmaa4Rw81a3a1VEx4LxB7HADUAXvZFhCoRdBzsMZyZmqHD
Error: no repository found at /Users/jbenet/.go-ipfs
Did you run `ipfs init` ?

This error message used to be correct, i believe. in any case, it's an error that tons of people are bound to hit. Maybe this is a case where we should have error message tests.

cc @whyrusleeping @chriscool
@chriscool
Copy link
Contributor

Ok, yeah you are right that it is perhaps better to check the error message then.

@whyrusleeping
Copy link
Member

Yeah, every bit of the UX should be tested

@whyrusleeping whyrusleeping added kind/bug A bug in existing code (including security flaws) topic/commands Topic commands topic/cleanup Topic cleanup labels Apr 12, 2015
@rht rht mentioned this issue May 26, 2015
Merged
@whyrusleeping whyrusleeping mentioned this issue May 26, 2015
Closed
49 tasks
@whyrusleeping whyrusleeping mentioned this issue Jun 2, 2015
Closed
58 tasks
@whyrusleeping whyrusleeping mentioned this issue Jun 9, 2015
Closed
50 tasks
@whyrusleeping
Copy link
Member

this has been resolved

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
kind/bug A bug in existing code (including security flaws) topic/cleanup Topic cleanup topic/commands Topic commands
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@jbenet @chriscool @whyrusleeping