[tahoe-lafs-trac-stream] [tahoe-lafs] #1744: The documentation of the "slot_testv_and_readv_and_writev" method in interfaces.py requires clarification.

[tahoe-lafs]

#1744: The documentation of the "slot_testv_and_readv_and_writev" method in
interfaces.py requires clarification.
-------------------------------+-------------------------------------
     Reporter:  zancas         |      Owner:  zancas
         Type:  defect         |     Status:  new
     Priority:  normal         |  Milestone:  1.9.2
    Component:  documentation  |    Version:  1.9.1
   Resolution:                 |   Keywords:  usability docs reviewed
Launchpad Bug:                 |
-------------------------------+-------------------------------------
Changes (by davidsarah):

 * keywords:  usability docs => usability docs reviewed
 * owner:   => zancas
 * milestone:  undecided => 1.9.2


Comment:

 +1, but I think the sentence "Of course, the extracted data contains no
 information about shares written to new shares that did not previously
 exist." is redundant, since it's implied by "old data" and "extant
 shares".

 Please also apply the following diff:
 {{{
 @@ -204,7 +204,9 @@

          The write vector will be applied to the given share, expanding it
 if
          necessary. A write vector applied to a share number that did not
 -        exist previously will cause that share to be created.
 +        exist previously will cause that share to be created. Write
 vectors
 +        must not overlap (if they do, this will either cause an error or
 +        apply them in an unspecified order).

          In Tahoe-LAFS v1.8.3 or later (except 1.9.0a1), if you send a
 write
          vector whose offset is beyond the end of the current data, the
 space

 }}}

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