This is a digestible behavior at this level, so we can implement a high-level abstraction on top of it. So let's first clarify how seed_mode is really supposed to work (it wouldn't be good if one undefined/unexpected behavior was fixed by adding another instead).ĪFAIK, torrent_finished_alert is posted each time the torrent goes from any "unfinished" state (some kind of checking or downloading state) into any "finished" one (finished or seed). Given that this ticket is closed, does that mean there is likely nothing to be done on the qbt side? Meaning fastresume_rejected_alert was generated for both. This message is consistent in both cases. 9:55 AM - File sizes mismatch for torrent 'xyz', pausing it. This happens in seed mode ^ Extra info(if any)
If you resume the torrent, It will start seeding instead of a recheck! Because missing files state was not registered! So the missing files torrent state didn't get registered at all. The torrent gets paused because of a missing files error.īut there's no sign of error in the transfer list. Steps to reproduceĪdd a torrent in seed mode(you need to have the files already for the seed mode to work) and exit qBt. This happens without seed mode ^ which is the expected behaviour. Torrents added in seed mode(skip hash check) does not register missing files state on startup if files are missing. Please provide the following information qBittorrent version and Operating System
0 kommentar(er)
