[tahoe-lafs-trac-stream] [tahoe-lafs] #1678: S3 backend: either handle or avoid truncated get_bucket responses

[tahoe-lafs]

#1678: S3 backend: either handle or avoid truncated get_bucket responses
------------------------------+-------------------------------------
     Reporter:  davidsarah    |      Owner:  davidsarah
         Type:  defect        |     Status:  new
     Priority:  critical      |  Milestone:  soon
    Component:  code-storage  |    Version:  1.9.0-s3branch
   Resolution:                |   Keywords:  s3-backend 410 reviewed
Launchpad Bug:                |
------------------------------+-------------------------------------

Comment (by davidsarah):

 Actually the patch is basically correct. It appeared not to be because we
 were incorrectly reporting all queries as truncated. (I thought that
 {{{BucketListing.is_truncated}}} was a boolean rather than a string, and
 the string {{{"false"}}} is truthy. Down with implicit conversions!)

 However, it turns out that truncated queries are ''not'' the cause of
 #1590 :-(

 I'll post an updated patch for this ticket, fixing the incorrect detection
 of truncated queries, tomorrow.

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