repair results Summary field says "Unhealthy" even though it is healthy after the repair, if it was unhealthy before #766

New Issue

Open

opened 2009-07-18 13:29:41 +00:00 by zooko · 6 comments

zooko commented

2009-07-18 13:29:41 +00:00

Here is the result of a deep check and repair, followed the the result of another deep check and repair a few minutes later on the same directory. I think the Summary field is wrong in the first one when it says that the directories are unhealthy. The right thing to say is that the directories were unhealthy before the repair, but are healthy now.

Here is the result of a deep check and repair, followed the the result of another deep check and repair a few minutes later on the same directory. I think the Summary field is wrong in the first one when it says that the directories are unhealthy. The right thing to say is that the directories *were* unhealthy before the repair, but are healthy now.

zooko added the

code-frontend-web

labels 2009-07-18 13:29:41 +00:00

zooko added this to the undecided milestone 2009-07-18 13:29:41 +00:00

zooko commented

2009-07-18 13:29:47 +00:00

Author

Attachment deep-check-and-repair-results.html (5269 bytes) added

**Attachment** deep-check-and-repair-results.html (5269 bytes) added

deep-check-and-repair-results.html

5.1 KiB

zooko commented

2009-07-18 13:30:17 +00:00

Author

Attachment deep-check-and-repair-results-2.html (4672 bytes) added

**Attachment** deep-check-and-repair-results-2.html (4672 bytes) added

deep-check-and-repair-results-2.html

4.6 KiB

tahoe-lafs modified the milestone from undecided to 1.7.0

2010-02-02 03:08:05 +00:00

zooko commented

2010-02-15 04:32:34 +00:00

Author

This is marked as "easy" and it is (in my opinion) a bug-fix rather than a feature-add so I would consider it a candidate for v1.6.1.

This is marked as "easy" and it is (in my opinion) a bug-fix rather than a feature-add so I would consider it a candidate for v1.6.1.

zooko modified the milestone from 1.7.0 to 1.6.1

2010-02-15 04:32:34 +00:00

davidsarah commented

2010-02-27 08:36:32 +00:00

Owner

Sorry, not going to have enough time to do this for 1.6.1.

Sorry, not going to have enough time to do this for 1.6.1.

tahoe-lafs modified the milestone from 1.6.1 to 1.7.0

2010-02-27 08:36:32 +00:00

tahoe-lafs modified the milestone from 1.7.0 to soon

2010-06-12 21:10:45 +00:00

tahoe-lafs modified the milestone from soon to 1.8β

2010-07-17 03:53:54 +00:00

davidsarah commented

2010-09-11 00:33:57 +00:00

Owner

Out of time for 1.8.

Out of time for 1.8.

tahoe-lafs modified the milestone from 1.8β to 1.9.0

2010-09-11 00:33:57 +00:00

tahoe-lafs modified the milestone from 1.9.0 to soon

2011-08-14 01:08:42 +00:00

tahoe-lafs modified the milestone from soon to 1.11.0

2012-04-05 19:47:34 +00:00

Lcstyle commented

2014-09-27 02:24:58 +00:00

Owner

if someone provides me with information on how to make a folder unhealthy, I might be able to knock this one out.

if someone provides me with information on how to make a folder unhealthy, I might be able to knock this one out.

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

2 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#766

No description provided.