"Added" field filled incorrectly in thin client
Posted: Mon May 18, 2015 4:59 pm
Hi, I have a 1.3.11 Windows client connected to a local 1.3.11 Debian daemon. Whenever I add several torrents consequently (i.e. a ~30 second delay between each, but it can be shorter / longer), the "Added" field gets filled with the same timestamp. Here's an example:
As a result, when I try sorting by that column, the affected torrents appear in a random order (you can tell by the "#" field in the screenshot above), which affects my day-to-day usage (for example, it's harder to find which episode I stopped at). If I were to add another torrent, say, half an hour later, it would get filled with a new timestamp, but usually it's behind the actual time of addition (like 10 seconds, +/-).
Is this some weird optimization gone wrong? Anybody else experiencing something like this?
As a result, when I try sorting by that column, the affected torrents appear in a random order (you can tell by the "#" field in the screenshot above), which affects my day-to-day usage (for example, it's harder to find which episode I stopped at). If I were to add another torrent, say, half an hour later, it would get filled with a new timestamp, but usually it's behind the actual time of addition (like 10 seconds, +/-).
Is this some weird optimization gone wrong? Anybody else experiencing something like this?