You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
When I tried using the program, I got the following message:
"Can't process convert resume.dat" and after ~30 seconds the console becomes responsive again.
After many experiments, I found what was causing this - if the trackers in the list are not properly separated by an empty line, it fails. Such trackers appear as a separate "ITEM" subgroup in the BEncode Editor.
Please account for such cases by implementing functionality which fixes such occurrences.
To Reproduce
I'm attaching an archive containing example resume.dat files and torrents - one is BAD, and the other one has been manually FIXED. DAT.torr.zip
Steps to reproduce the behavior:
Run the program with command pointing to the directory containing the extracted BAD resume.dat file
See error
Expected behavior
The program should complete the procedure successfully. It should account for cases like this and fix occurrences of trackers not separated by empty line (as seen in the uTorrent Torrent Properties window), or empty tracker lines (three consecutive empty lines, as seen in the uTorrent Torrent Properties window, see the first attached screenshot below).
An extra request
Please consider adding the option to display more details why the program fails, why it can't process the resume.dat file. I fear that even if the issue above is fixed, there will be other issues with some of the rest of my torrents (~3400 in total).
Screenshots
Screenshots to help explain the problem and the solution. They were taken in Win10 to avoid messing all my torrents on the Win7 machine:
The text was updated successfully, but these errors were encountered:
Just a quick update - I'm ashamed to say that even though I've been using uTorrent for over 15 years, I'm learning just now that it supported tracker tiers. 😊
According to the help file:
Does µTorrent support multi-tracker .torrent files?
Yes, µTorrent supports multi-tracker .torrent files. µTorrent announces to all tracker tiers simultaneously, but only one tracker per tier.
Apparently uTorrent treats trackers which are bundled one after another without a separating empty line (like the examples above, the ITEM sub-group) as a single tier, similarly to the qBittorrent tracker tier behavior I suppose.
If technically possible, please take this information into consideration when implementing the fix - basically "port" these tiers from uT to the qbt tiers, if you think it's a good idea.
Describe the bug
When I tried using the program, I got the following message:
"Can't process convert resume.dat" and after ~30 seconds the console becomes responsive again.
After many experiments, I found what was causing this - if the trackers in the list are not properly separated by an empty line, it fails. Such trackers appear as a separate "ITEM" subgroup in the BEncode Editor.
Please account for such cases by implementing functionality which fixes such occurrences.
To Reproduce
I'm attaching an archive containing example resume.dat files and torrents - one is BAD, and the other one has been manually FIXED.
DAT.torr.zip
Steps to reproduce the behavior:
Expected behavior
The program should complete the procedure successfully. It should account for cases like this and fix occurrences of trackers not separated by empty line (as seen in the uTorrent Torrent Properties window), or empty tracker lines (three consecutive empty lines, as seen in the uTorrent Torrent Properties window, see the first attached screenshot below).
Desktop:
An extra request
Please consider adding the option to display more details why the program fails, why it can't process the resume.dat file. I fear that even if the issue above is fixed, there will be other issues with some of the rest of my torrents (~3400 in total).
Screenshots
Screenshots to help explain the problem and the solution.
They were taken in Win10 to avoid messing all my torrents on the Win7 machine:
The text was updated successfully, but these errors were encountered: