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

Unable to load torrent file - Failed to parse torrent "malformed bencode: Integer delimiter not found." #169

Closed
FrAcTi0N opened this issue Feb 21, 2024 · 8 comments
Labels
fix-committed Fix for the issue is in the main branch

Comments

@FrAcTi0N
Copy link

Unable to load some torrent files, showing:
Error reading torrent
Failed to parse torrent

bellow is a log from CMD

./TrguiNG 
2024-02-21 22:49:20.434 TrguiNG[28907:7030376] WARNING: Secure coding is not enabled for restorable state! Enable secure coding by implementing NSApplicationDelegate.applicationSupportsSecureRestorableState: and returning YES.
Got response: TrguiNG OK
Got response: TrguiNG OK
Failed to parse torrent "malformed bencode: Integer delimiter not found."
@qu1ck
Copy link
Member

qu1ck commented Feb 22, 2024

I can't fix it if you don't provide an example of such torrent

@FrAcTi0N
Copy link
Author

FrAcTi0N commented Feb 22, 2024

Sorry, i am unable to add it as an attachment, so i will paste the content here, is this enough?

`

@qu1ck
Copy link
Member

qu1ck commented Feb 22, 2024

You can't post binary data into a comment and expect it to not be all kinds of broken :D

Upload the file on some file share site, like dropbox or https://filetransfer.io/

@FrAcTi0N
Copy link
Author

i thought that, sorry, here is the link.
https://filetransfer.io/data-package/T2epff0w#link

qu1ck added a commit that referenced this issue Feb 22, 2024
It has a fix for torrent files with junk at the end tripping
the parser

Issue #169
@qu1ck qu1ck added the fix-committed Fix for the issue is in the main branch label Feb 22, 2024
@qu1ck
Copy link
Member

qu1ck commented Feb 22, 2024

That torrent file has a random "eol" character at the end of it which makes it technically malformed. I pushed a fix though so next version will not trip up on it.

In the meantime you can add such files through the web interface.

@FrAcTi0N
Copy link
Author

TY, will let you know after the new release if it get fixed.

@FrAcTi0N
Copy link
Author

I just compiled current GitHub version and I can confirm it's working. TY.

@qu1ck
Copy link
Member

qu1ck commented Apr 15, 2024

Fixed in v1.3.0

@qu1ck qu1ck closed this as completed Apr 15, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
fix-committed Fix for the issue is in the main branch
Projects
None yet
Development

No branches or pull requests

2 participants