Opened at 2010-07-07T18:29:20Z

Last modified at 2010-07-15T16:14:24Z

#1112 new defect

error message for corrupted caps to {{{tahoe ls}}} is unclear

Reported by: zooko Owned by:
Priority: major Milestone: soon
Component: code-frontend-cli Version: 1.7.0
Keywords: tahoe-ls usability newurls error Cc:
Launchpad Bug:

Description

This is the write-cap and the read-cap respectively to the same dir: 

$ tahoe ls --node-url=http://127.0.0.1:3456 URI:DIR2:77mdr6nhhzqo22lvviojxbqooy:dkkrzum2rynr2sxunwn5n7arusmuxw3m27k3f4yo2t67rqzz6xiaa


This listing included unknown objects. Using a webapi server that supports
a later version of Tahoe may help.
$ tahoe ls --node-url=http://127.0.0.1:3456 URI:DIR2-RO:c4kxgewzc4r7stpoo5e3rvwozy:dkkrzum2rynr2sxunwn5n7arusmuxw3m27k3f4yo2t67rqzz6xia
Negativeland_on_Radio1190.org.ogg

Change History (3)

comment:1 Changed at 2010-07-12T04:55:37Z by davidsarah

  • Keywords newurls error added

The write cap ends with 'xiaa', the read cap with 'xia'. Presumably the latter is correct.

Probably we should assume that future caps don't start with known prefixes (in this case URI:DIR2:), so that we could print a more sensible message.

comment:2 Changed at 2010-07-12T04:57:35Z by davidsarah

Also, an unknown directory doesn't include unknown objects, it is an unknown object. So the message could be improved in any case.

comment:3 Changed at 2010-07-15T16:14:24Z by zooko

  • Summary changed from tahoe ls with dir-write-cap fails mysteriously, with dir-read-cap works to error message for corrupted caps to {{{tahoe ls}}} is unclear
Note: See TracTickets for help on using tickets.