[tahoe-dev] [tahoe-lafs] #819: allmydata.test.test_repairer.Verifier.test_corrupt_crypttext_hashtree failed

[tahoe-lafs]

#819: allmydata.test.test_repairer.Verifier.test_corrupt_crypttext_hashtree
failed
-----------------------+----------------------------------------------------
 Reporter:  zooko      |           Owner:  zooko    
     Type:  defect     |          Status:  assigned 
 Priority:  critical   |       Milestone:  undecided
Component:  code       |         Version:  1.5.0    
 Keywords:  integrity  |   Launchpad_bug:           
-----------------------+----------------------------------------------------

Comment(by warner):

 What was the seed? If you set the seed to that value, can you reproduce
 the failure?
 If you can help me reproduce it, I can help track it down.

 My hunch is that the verifier is not quite looking at the whole share. The
 Verifier (whose job is to fetch and verify every byte of every share)
 shares a lot of code with the Downloader (whose job is to fetch as few
 bytes as possible). So any shortcuts that the Downloader takes must be
 worked around by the Verifier, and it's easy to miss some.

 The new Downloader that I'm slowly developing (for #287) will be even more
 specialized for minimum-fetching, so I think it'll soon be time to stop
 sharing much code between the two pieces.

-- 
Ticket URL: <http://allmydata.org/trac/tahoe/ticket/819#comment:4>
tahoe-lafs <http://allmydata.org>
secure decentralized file storage grid