Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

"Can't process convert resume.dat" when trackers are not perfectly separated by empty lines [uTorrent 2.2.1] #37

Closed
zerofool opened this issue Apr 7, 2022 · 3 comments

Comments

@zerofool
Copy link

zerofool commented Apr 7, 2022

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:

  1. Run the program with command pointing to the directory containing the extracted BAD resume.dat file
  2. 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).

Desktop:

  • OS: Windows 7 Ultimate x64 SP1
  • Versions: uTorrent 2.2.1 Build 25154; bt2qbt 1.11, 1.12, 1.13, 1.14, 1.15

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:
torr1_BADvsFixed
torr2_BADvsFixed
torr3_BADvsFixed
torr4_BADvsFixed

@rumanzo
Copy link
Owner

rumanzo commented Apr 7, 2022

You made great work! Will fix it soon

@zerofool
Copy link
Author

zerofool commented Apr 8, 2022

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.

@rumanzo
Copy link
Owner

rumanzo commented Apr 8, 2022

I rewrited handling trackers function and add functionality for different tiers. Check it out
b66b5f8
https://github.com/rumanzo/bt2qbt/releases/tag/v1.16
Let me know if it helps you

@rumanzo rumanzo closed this as completed Apr 17, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants