miscalculated downloading-time-seconds vs seeding-time-seconds on new, existing torrents

[reardonia]

What is the issue?

in Tr4 mainline:

Something changed in the logic handling seeding-time and downloading-time, likely with 7e8eca0.

If I (re)add a torrent for which the file(s) exist already, the done-date is set to zero. The torrent is never "done" because it never begins downloading. It remains in a state where donwloading-time-seconds increases forever, but seeding-time-seconds remains at zero.

Which application of Transmission?

transmission-daemon

Which version of Transmission?

Tr4 mainline

[killemov]

I just ran a test with Shift + 4.0.5 (a6fe2a64aa) and I can't reproduce the described behavior. After re-adding it starts seeding after checking. doneDate has data and secondsSeeding is counting.

[reardonia]

I just ran a test with Shift + 4.0.5 (a6fe2a6) and I can't reproduce the described behavior. After re-adding it starts seeding after checking. doneDate has data and secondsSeeding is counting.

mainline not 4.0.x

[tearfur]

I couldn't reproduce on d42d0f3f3f50c01cda1d9f7180d1f4a3ef8aba63 either...

[tearfur]

Closing for now due to lack of response.

[reardonia]

could you please reopen this. just have a lot of issues&bugs that I'm slowly working through. This one is still a priority as its still happening on my systems. I'm trying to find the cause or at least a crisp repro.