zero-length reads break new mutable downloader #1512

Closed
opened 2011-08-27 23:55:46 +00:00 by warner · 3 comments

The new mutable downloader, landed as part of MDMF in #393, has problems when asked to download zero bytes: it returns more than zero bytes.

We have tests in test_mutable.Version to catch this, currently disabled.

This is a blocker for 1.9beta

The new mutable downloader, landed as part of MDMF in #393, has problems when asked to download zero bytes: it returns more than zero bytes. We have tests in `test_mutable.Version` to catch this, currently disabled. This is a blocker for 1.9beta
warner added the
code-mutable
major
defect
1.9.0a1
labels 2011-08-27 23:55:46 +00:00
warner added this to the 1.9.0 milestone 2011-08-27 23:55:46 +00:00
kevan commented 2011-08-30 21:09:41 +00:00
Owner

Attachment fix-zero-length-reads.darcspatch (10049 bytes) added

fix zero-length reads; enable tests of zero-length reads

**Attachment** fix-zero-length-reads.darcspatch (10049 bytes) added fix zero-length reads; enable tests of zero-length reads
Kevan Carstensen <kevan@isnotajoke.com> commented 2011-08-31 05:10:23 +00:00
Owner

In changeset:32e30c9023479e3c:

mutable/retrieve: handle the case where self._read_length is 0.

Note that the downloader will still fetch a segment for a zero-length
read, which is wasteful. Fixing that isn't specifically required to fix
#1512, but it should probably be fixed before 1.9.
In changeset:32e30c9023479e3c: ``` mutable/retrieve: handle the case where self._read_length is 0. Note that the downloader will still fetch a segment for a zero-length read, which is wasteful. Fixing that isn't specifically required to fix #1512, but it should probably be fixed before 1.9. ```
tahoe-lafs added the
fixed
label 2011-08-31 05:10:23 +00:00
Author

I agree with the comment that it'd be nice to improve efficiency of zero-byte reads by not actually downloading any segments (I've opened #1518 to track that), but I'm not going to hold up 1.9 for that.. correctness is sufficient.

I agree with the comment that it'd be nice to improve efficiency of zero-byte reads by not actually downloading any segments (I've opened #1518 to track that), but I'm not going to hold up 1.9 for that.. correctness is sufficient.
Sign in to join this conversation.
No Milestone
No Assignees
2 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

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