Improved HTTP response length handling #1204
No reviewers
Labels
No Label
Benchmarking and Performance
HTTP Storage Protocol
Nevow Removal
Python 3 Porting
not-for-merge
No Milestone
No project
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: tahoe-lafs/tahoe-lafs#1204
Loading…
Reference in New Issue
No description provided.
Delete Branch "3907-http-response-lengths"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Fixes https://tahoe-lafs.org/trac/tahoe-lafs/ticket/3907
There's a few error handling codepaths that aren't handled, like "mutable changed out from under you" or "there's a bug!". Can try to figure something out if reviewer feels it's useful.
BOOOOOO
Coverage decreased (-0.04%) to 94.701% when pulling
94e0568653
on 3907-http-response-lengths into69f90e6336
on master.Thanks. Looks good. Some minor comments inline. Please address those and then merge.
Content-Range
could be missing from the response header here, I think?@ -204,0 +207,4 @@
"""
Return the length of the data in the share, if we're reading.
"""
return self._length
a docstring here would be nice
and here
@ -420,2 +421,4 @@
f.close()
return data_length
def check_write_enabler(self, write_enabler, si_s):
and here
This could go directly to
ShareFile
I think?Ended up deleting this method, per later comment.