[tahoe-dev] [tahoe-lafs] #837: 'tahoe ls' on unknown objects: error message should be clearer

[tahoe-lafs]

#837: 'tahoe ls' on unknown objects: error message should be clearer
-------------------------------+--------------------------------------------
 Reporter:  warner             |           Owner:           
     Type:  defect             |          Status:  new      
 Priority:  major              |       Milestone:  undecided
Component:  code-frontend-cli  |         Version:  1.5.0    
 Keywords:                     |   Launchpad_bug:           
-------------------------------+--------------------------------------------
 If you list a directory with {{{tahoe ls}}}, and it happens to
 contain an object that your client doesn't recognize (say, a cap
 type from the future, like DIR-IMM from a pre-1.6 client), the
 child name is displayed normally. If you then try to list that
 object, you get an error message (because your client doesn't
 know how to download or interpret it), that looks like this:

 {{{
 % ./bin/tahoe ls alias:source-backups/Latest
 Error during GET: 400 Bad Request GET unknown: can only do t=info, not
 t=json
 }}}

 We should make this error message more informative. The key word
 in the message is "unknown", and means (from the point of view of
 the code that emits it) that the {{{IFilesystemNode}}} object you
 pointed at is of type {{{UnknownNode}}} (as opposed to
 {{{IFileNode}}} or {{{IDirectoryNode}}} or something else it
 knows how to handle).

 The CLI side should probably spot the webapi error message
 ({{{if "unknown: can only do t=info" in data}}}) and append
 something helpful, like "This means you tried to list a
 filesystem object that was unrecognized by your tahoe client,
 probably because it was created by a newer version. Upgrading
 your tahoe client to the latest version may enable you to use
 this object."""

-- 
Ticket URL: <http://allmydata.org/trac/tahoe/ticket/837>
tahoe-lafs <http://allmydata.org>
secure decentralized file storage grid