diff options
| author |  Joey Hess <joeyh@joeyh.name> | 2016-12-08 16:00:29 -0400 |
|---|---|---|
| committer | Joey Hess <joeyh@joeyh.name> | 2016-12-08 16:00:29 -0400 |
| commit | 0ab80b705055528cd3858870e5f5eb88b9b71d92 (patch) | |
| tree | 3abe6b587ce915872150eb4648d51701e01794a1 /doc/todo/tor.mdwn | |
| parent | d492965b712dbe3ab9dbc8f6526ba5f1aed13a4f (diff) | |
update
Diffstat (limited to 'doc/todo/tor.mdwn')
| -rw-r--r-- | doc/todo/tor.mdwn | 6 |
1 files changed, 4 insertions, 2 deletions
diff --git a/doc/todo/tor.mdwn b/doc/todo/tor.mdwn index 12ef7561f..b262c793c 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? |