From 39b7eb73506836416efb3d1b5ba95c894506d025 Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Thu, 8 Dec 2016 16:00:29 -0400 Subject: [PATCH] update --- doc/todo/tor.mdwn | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/doc/todo/tor.mdwn b/doc/todo/tor.mdwn index 12ef7561f1..b262c793c6 100644 --- a/doc/todo/tor.mdwn +++ b/doc/todo/tor.mdwn @@ -6,8 +6,10 @@ Current todo list: * copy --to peer seems to make the remotedaemon buffer the content in memory, more than I'd expect. Check if this is a memory leak.. -* Resuming an interrupted transfer fails at the end, despite having gotten - the whole correct file content. +* When a transfer can't be done because another transfer of the same + object is already in progress, the message about this is output by the + remotedaemon --debug, but not forwarded to the peer, which shows + "Connection reset by peer" * update progress logs in remotedaemon send/receive * Think about locking some more. What happens if the connection to the peer is dropped while we think we're locking content there from being dropped?