test for interrupted writes of mutable files #270

Open
opened 2008-01-11 01:18:34 +00:00 by zooko · 1 comment
zooko commented 2008-01-11 01:18:34 +00:00
Owner

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.

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.
tahoe-lafs added the
code-encoding
major
defect
0.7.0
labels 2008-01-11 01:18:34 +00:00
tahoe-lafs added this to the eventually milestone 2008-01-11 01:18:34 +00:00
tahoe-lafs added
code-mutable
and removed
code-encoding
labels 2008-04-24 23:31:30 +00:00
zooko commented 2010-05-26 14:50:23 +00:00
Author
Owner

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. :-)

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. :-)
tahoe-lafs modified the milestone from eventually to 1.8.0 2010-05-26 14:50:23 +00:00
tahoe-lafs modified the milestone from 1.8.0 to 1.9.0 2010-08-10 03:44:30 +00:00
tahoe-lafs modified the milestone from 1.9.0 to 1.10.0 2011-08-29 15:30:27 +00:00
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: tahoe-lafs/trac-2024-07-25#270
No description provided.