Opened at 2008-01-11T01:18:34Z
Last modified at 2011-08-29T15:30:27Z
#270 new defect
test for interrupted writes of mutable files
| Reported by: | zooko | Owned by: | zooko |
|---|---|---|---|
| Priority: | major | Milestone: | soon |
| Component: | code-mutable | Version: | 0.7.0 |
| Keywords: | reliability preservation test | Cc: | |
| Launchpad Bug: |
Description
We don't have a unit test which shows what happens when client and/or servers are interrupted when the client is updating a mutable file, and then the client later tries again. It should be the case that eventually, once an update succeeds, that all the shares are brought up to date.
Change History (7)
comment:1 Changed at 2008-04-24T23:31:30Z by warner
- Component changed from code-encoding to code-mutable
comment:2 Changed at 2009-10-28T07:15:08Z by davidsarah
- Keywords reliability tests added
comment:3 Changed at 2009-10-28T07:15:35Z by davidsarah
- Keywords test added; tests removed
comment:4 Changed at 2009-12-29T19:15:57Z by davidsarah
- Keywords preservation added
comment:5 Changed at 2010-05-26T14:50:23Z by zooko
- Milestone changed from eventually to 1.8.0
comment:6 Changed at 2010-08-10T03:44:30Z by davidsarah
- Milestone changed from 1.8.0 to 1.9.0
comment:7 Changed at 2011-08-29T15:30:27Z by warner
- Milestone changed from 1.9.0 to 1.10.0
Note: See
TracTickets for help on using
tickets.
It's really bothering me that mutable file upload and download behavior is so finicky, buggy, inefficient, hard to understand, different from immutable file upload and download behavior, etc. So I'm putting a bunch of tickets into the "1.8" Milestone. I am not, however, at this time, volunteering to work on these tickets, so it might be a mistake to put them into the 1.8 Milestone, but I really hope that someone else will volunteer or that I will decide to do it myself. :-)