Reduce implementation-dependency of IStorageServer
#1117
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#1117
Loading…
Reference in New Issue
No description provided.
Delete Branch "3779-istorageserver-with-fewer-assumptions"
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/3779
Left in the so-called "pipeline" code, since it's not clear if it's needed or not.
Update: Also fixed a pre-existing bug in remote_advise_corrupt_share that was exposed by the changes.
Hm. Getting the impression that I broke something with the seemingly minor tweaks I did...
Actually—those errors were probably there before, and just were being dropped on the floor, and now they're being logged.
@ -713,1 +712,4 @@
self.corruption_advisory_dir,
("%s--%s-%d" % (now, str(si_s, "utf-8"), shnum)).replace(":","")
)
with open(fn, "w") as f:
This is a (easy to miss) bugfix. Previously the replace was on the whole path, thus removing all colons from paths.
Coverage increased (+0.0007%) to 95.491% when pulling
fb61e29b59
on 3779-istorageserver-with-fewer-assumptions into056ee58e91
on master.Thanks. Minor comments inline. Please address and merge.
Can you make it clear here that this is about behavior for a storage server running on Windows (ie, it doesn't matter where the client is running)?
Passing a descriptive (or at least distinctive) reason to
log.err
will make it easier to make sense of any failures logged by this code path. Can you add that here and to the other newlog.err
errbacks?