#818 new enhancement

Output of tahoe deep-check --repair is hard to skim

Reported by: kpreid Owned by:
Priority: minor Milestone: 1.15.0
Component: code-frontend-cli Version: 1.4.1
Keywords: deep-check easy repair usability Cc: kpreid
Launchpad Bug:

Description (last modified by daira)

The summary output of tahoe deep-check looks exactly the same, except for the numbers, no matter whether everything is fine or files needed to be repaired. For easier scanning, especially in a log of multiple deep-check operations at different times or of different files, it should have fewer statements that there were 0 of something; for example, in the simple case of all files being healthy, a statement like “5 files checked and found healthy.” would be good, as opposed to the current:

done: 5 objects checked
 pre-repair: 5 healthy, 0 unhealthy
 0 repairs attempted, 0 successful, 0 failed
 post-repair: 5 healthy, 0 unhealthy

Also, the output does not include any feedback that --add-lease did its thing, but that is perhaps a separate issue.

Change History (7)

comment:1 Changed at 2009-10-26T03:15:15Z by zooko

  • Keywords easy added

Tagging this as "easy". (Feel free, kpreid or anyone, to untag it if this seems harder to you than "easy".)

comment:2 Changed at 2009-10-26T12:37:40Z by kpreid

  • Cc kpreid added

comment:3 Changed at 2009-12-06T00:20:11Z by davidsarah

  • Keywords repair usability added

comment:4 Changed at 2013-09-01T16:43:56Z by daira

  • Description modified (diff)
  • Milestone changed from undecided to 1.12.0

comment:5 Changed at 2016-03-22T05:02:25Z by warner

  • Milestone changed from 1.12.0 to 1.13.0

Milestone renamed

comment:6 Changed at 2016-06-28T18:17:14Z by warner

  • Milestone changed from 1.13.0 to 1.14.0

renaming milestone

comment:7 Changed at 2020-06-30T14:45:13Z by exarkun

  • Milestone changed from 1.14.0 to 1.15.0

Moving open issues out of closed milestones.

Note: See TracTickets for help on using tickets.