show full, explorable details about check and repair operations

[zooko]

On Mon, Jul 9, 2012 at 10:39 AM, Brad Rupp <bradrupp@gmail.com> wrote:
>
> The output from repair #1:
>
> repair successful
> done: 11801 objects checked
>  pre-repair: 11725 healthy, 76 unhealthy
>  76 repairs attempted, 76 successful, 0 failed
>  post-repair: 11801 healthy, 0 unhealthy
>
> The output from repair #2:
>
> done: 11801 objects checked
>  pre-repair: 11789 healthy, 12 unhealthy
>  12 repairs attempted, 11 successful, 1 failed
>  post-repair: 11800 healthy, 1 unhealthy
>
> As you can see, the first repair found and fixed 76 unhealthy objects. The
> second repair, approximately 12 hours later, found 12 unhealthy objects and
> fixed 11 of them.
>
> Why would the second repair find 12 unhealthy objects?  I would have
> expected it to find 0 unhealthy objects given that the first repair was
> performed only 12 hours earlier.

Wouldn't it be great if the text that said "12 repairs attempted, 11 successful, 1 failed" had hyperlinks to web pages that listed all of the repair attempts, where you could see which file was not healthy, which servers the repair job attempted to use to repair the file, and what happened with each server that led to success or failure?

Providing such a web page would mostly just be a matter of "web programming" -- generating HTML that shows the contents of the Python objects in memory which contain that data.

check-and-repair-results.xhtml

deep-check-and-repair-results.xhtml

upload-results.xhtml

publish-status.xhtml

Here's the data stored in Python objects in memory:

check_results.py

See this thread on the tahoe-dev list.