[tahoe-lafs-trac-stream] [tahoe-lafs] #1994: S3 Error during initialization of S3 store to use with S3(cloud) backend

[tahoe-lafs]

#1994: S3 Error during initialization of S3 store to use with S3(cloud) backend
------------------------------+-----------------------
     Reporter:  Zancas        |      Owner:  Zancas
         Type:  defect        |     Status:  new
     Priority:  normal        |  Milestone:  undecided
    Component:  code-storage  |    Version:  1.10.0
   Resolution:                |   Keywords:  cloud S3
Launchpad Bug:                |
------------------------------+-----------------------

Comment (by daira):

 Replying to [comment:3 Zancas]:
 > Replying to [comment:2 daira]:
 > > I was actually hoping to get the HTTP error code from the log, but
 txaws exception messages don't include that. (The error handling in Tahoe-
 LAFS' S3 code does include it.)
 >
 > Should we put adding HTTP error codes to txaws exceptions into a scrumdo
 story?

 I'd rather eliminate Tahoe-LAFS' dependency on txaws. All of the container
 implementations for other services are making direct HTTP requests, and
 {{{S3Container}}} could do the same without a significant increase in code
 size or complexity (given that we're having to override the HMAC signature
 computation anyway).

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