[tahoe-lafs-trac-stream] [tahoe-lafs] #1812: parse_abbreviated_size doesn't accept T for terabytes (and other quibbles with the regex it uses)

[tahoe-lafs]

#1812: parse_abbreviated_size doesn't accept T for terabytes (and other quibbles
with the regex it uses)
-------------------------+-------------------------------------------------
     Reporter:           |      Owner:  warner
  davidsarah             |     Status:  closed
         Type:  defect   |  Milestone:  1.10.0
     Priority:  minor    |    Version:  1.9.2
    Component:  code     |   Keywords:  reserved_space storage error
   Resolution:  fixed    |  usability needs-review
Launchpad Bug:           |
-------------------------+-------------------------------------------------
Changes (by David-Sarah Hopwood <david-sarah@…>):

 * status:  new => closed
 * resolution:   => fixed


Comment:

 In [changeset:b084396bddd1e12a5e49ed4e9f1a2eafcbe8e01b/git]:
 {{{
 #!CommitTicketReference repository="git"
 revision="b084396bddd1e12a5e49ed4e9f1a2eafcbe8e01b"
 client.py: throw error when reserved_space= is unparseable. Closes #1812.

 This should now fail quickly (during "tahoe start"). Previously this
 would silently treat an unparseable size as "0", and the only way to
 discover that it had had a problem would be to look at the foolscap log,
 or examine the storage-service web page for the unexpected "Reserved
 Size" number.
 }}}

-- 
Ticket URL: <https://tahoe-lafs.org/trac/tahoe-lafs/ticket/1812#comment:19>
tahoe-lafs <https://tahoe-lafs.org>
secure decentralized storage