Opened at 2012-06-08T15:52:30Z
Last modified at 2012-06-09T03:29:52Z
#1763 new defect
NoServersError raised to user
Reported by: | zooko | Owned by: | |
---|---|---|---|
Priority: | normal | Milestone: | undecided |
Component: | code-frontend-cli | Version: | 1.9.1 |
Keywords: | usability cli error | Cc: | |
Launchpad Bug: |
Description
\"/home/some/Downloads/allmydata-tahoe-1.9.0-r5844/src/allmydata/immutable/ upload.py\", line 213, in get_shareholders\x0a raise NoServersError(\"client gave us zero servers\")\x0aallmydata.interfaces.NoServersError: client gave us zero
This is an example of "stack traces should never be displayed to the user". Instead, the cli should catch exceptions of this type and print out a nice explanation to the user about what is wrong and how to diagnose and fix it.
Change History (2)
comment:1 follow-up: ↓ 2 Changed at 2012-06-08T22:05:44Z by warner
comment:2 in reply to: ↑ 1 Changed at 2012-06-09T03:29:52Z by zooko
Replying to warner:
so, um, what command were you running when you got this message?
Sorry. The command was:
./bin/tahoe put file.ext
Note: See
TracTickets for help on using
tickets.
so, um, what command were you running when you got this message?
The fact that we're using HTTP for everything is a bit of a drag.. either we need to format everything for a possible CLI command in the webapi, or the CLI code needs to interpret some machine-oriented HTTP response and come up with something human facing (after we've already thrown out a lot of the information). The webapi side is probably easier to do.