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

New Issue

Open

opened 2009-10-26 03:01:55 +00:00 by kpreid · 5 comments

kpreid commented

2009-10-26 03:01:55 +00:00

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.

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.

kpreid added the

code-frontend-cli

labels 2009-10-26 03:01:55 +00:00

kpreid added this to the undecided milestone 2009-10-26 03:01:55 +00:00

zooko commented

2009-10-26 03:15:15 +00:00

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

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

tahoe-lafs modified the milestone from undecided to 1.12.0

2013-09-01 16:43:56 +00:00

warner commented

2016-03-22 05:02:25 +00:00

Milestone renamed

Milestone renamed

warner modified the milestone from 1.12.0 to 1.13.0

2016-03-22 05:02:25 +00:00

warner commented

2016-06-28 18:17:14 +00:00

renaming milestone

renaming milestone

warner modified the milestone from 1.13.0 to 1.14.0

2016-06-28 18:17:14 +00:00

exarkun commented

2020-06-30 14:45:13 +00:00

Moving open issues out of closed milestones.

Moving open issues out of closed milestones.

exarkun modified the milestone from 1.14.0 to 1.15.0

2020-06-30 14:45:13 +00:00

meejah commented

2021-03-30 18:40:19 +00:00

Owner

Ticket retargeted after milestone closed

Ticket retargeted after milestone closed

meejah modified the milestone from 1.15.0 to soon

2021-03-30 18:40:19 +00:00

Sign in to join this conversation.

No Label

LeastAuthority.com automation

cannot reproduce

code-frontend-cli

code-frontend-ftp-sftp

code-frontend-magic-folder

code-frontend-web

code-peerselection

dev-infrastructure

somebody else's problem

was already fixed

No Milestone

No Assignees

5 Participants

Notifications

Due Date

The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Reference: tahoe-lafs/trac-2024-07-25#818

No description provided.