[tahoe-lafs-trac-stream] [tahoe-lafs] #1679: Potential download regression 1.9.1 versus 1.8.3

[tahoe-lafs]

#1679: Potential download regression 1.9.1 versus 1.8.3
--------------------------+---------------------------------
     Reporter:  nejucomo  |      Owner:  nobody
         Type:  defect    |     Status:  new
     Priority:  critical  |  Milestone:  1.9.2
    Component:  unknown   |    Version:  1.9.1
   Resolution:            |   Keywords:  regression download
Launchpad Bug:            |
--------------------------+---------------------------------

Comment (by nejucomo):

 Why do you suggest it's a regression?  Both client versions display
 similar behavior at different times.

 It could be a storage server or introducer regression.

 Again, to summarize the most salient aspects:

 * The failure is transient.
 * The failure occurs when retrieving content with $CHK_CAP directly and
 sometimes via $DIR2_RO_CAP/index.html.
 * Sometimes the $CHK_CAP retrieval fails while the $DIR2_RO_CAP/index.html
 succeeds on the same gateway!
 * Both 1.8.3 and 1.9.1 gateways have displayed similar behavior at
 different times.


 It's very mysterious to me that two different retrieval methods for the
 same content fail or succeed respectively.

 Maybe the retrieval method is a red-herring and instead there is some
 networking connectivity, caching, or other transient state which changes
 in a poorly handled / detected edge case.

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