Opened at 2010-10-28T23:23:19Z
Last modified at 2011-08-13T23:31:46Z
#1234 assigned defect
UnrecoverableFileError message should say which file it refers to — at Initial Version
| Reported by: | davidsarah | Owned by: | |
|---|---|---|---|
| Priority: | major | Milestone: | soon |
| Component: | code-frontend-web | Version: | 1.8.0 |
| Keywords: | error usability capleak | Cc: | |
| Launchpad Bug: |
Description
zooko on irc:
sigh, I am experiencing failure using the pub test grid :-/
My top-level directory contains some subdir or subdir of subdir which is unrecoverable.
Therefore, as far as I know, the Tahoe-LAFS UIs provide almost no way to proceed.
I can't deep-repair, I can't cp -r to recover the recoverable stuff.
Maybe I can deep-check to learn which one is unrecoverable ...
ticket:755#comment:4 mentions this problem, but that ticket is mainly about having deep-check continue on error. Giving information about which file is unrecoverable (the cap, and the filename if known) would be useful in more circumstances than just deep-check.
Note that because of #625, we need a write cap to repair mutable files/directories. Otherwise I would suggest diminishing the cap in the message to a read or verify cap (since the error message channel might be more vulnerable to cap leakage). As it is, the user needs the write cap, at least for mutable objects.
