That's how it should be, but isn't the case for me. Can you confirm the deluge version you're running?

timelesspa wrote: ↑Wed Feb 02, 2022 11:29 pm what settings would be best to use for removing on completion?

Hard to say. It's like someone asking "what's best food". It all depends on your wants and needs for removal logic.

I'd recommend going with docker for older versions. debian:buster-slim image would install 1.3.15 by default.

If you only want the thin client to connect to your server, you can check out the dockerfile I'm using: https://github.com/laur89/deluge-gtk-1.3.15-docker

> debug-logging enabled That's probably why you're seeing it. I'm not explicitly setting any logging levels when starting deluge. And this is how I was running it during the v1.3 days as well - it kept the logfile quiet, but errors still were logged. Don't really see a case where I wouldn't want to ...

Nope, you understood perfectly. Then it's odd what's going on here. My plugin is logging line such as log.error("test err") but ~/.config/deluge/deluge.log remains empty. Only when deluge fails to start is when something is written to that file, eg Cannot start deluged, listen port in use....

Updated all 1.3 plugins I'm using to support deluge 2.0.5, including the required logging change import logging log = logging.getLogger(__name__) but noticed log.error() level is not being logged by default, ie nothing is logged to deluge.log at all. Is this expected? Error level used to be logged b...

Cool, thanks for looking into it as always.

Just checked the files - there is a .pad/ directory 69.5MiB in size listed, so that confirms your theory. So guess it settles this. deluge2 only shows both when there's a diff Think you're slightly wrong here. Those two values (separated by a slash) isn't designating padded & un-padded values pe...

Huh, interesting. So torrents often contain padding data? Is it something on the protocol level, or what torrent uploaders themselves need to explicitly create/define? Also, does this also mean there's no way to know how much space a torrent will take on a drive once it's completed, based on console...

Sorry think I'm not following. Are you claiming it's correct output from the console, given the torrent actually has completed downloading & is now seeding? To me it appears that it thinks 0.1G remains to be downloaded (50.8 < 50.9), but that's not really the case. Note the whole torrent was dow...