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

Server, client to behave weird if an announced torrent contains only empty files #234

Open
mbait opened this issue Dec 20, 2018 · 3 comments

Comments

@mbait
Copy link

mbait commented Dec 20, 2018

If a torrent contains only empty files, then the generated .torrent file won't open in Transmission (nothing happens, no "new torrent" dialog appears after selecting the file in the open file dialog). When I try to download the torrent with the means of ttorrent (SimpleClient.downloadTorrent()) it finishes, leaving .part-files for every file in the torrent. Adding a single byte to any file in the torrent and re-generating and re-announcing the torrent solves the problem: everything is downloaded correctly and the .torrent-file is opened in Transmission as expected. Perhaps, the issues is related to #233.

@Dead-off
Copy link
Collaborator

Thank you, i'll look at this issue and your previous issue next week!

@Dead-off
Copy link
Collaborator

i didn't find something about empty files in torrent protocol documentation. Also Qbittorrent client hangs with empty torrent file too. Looks like i can add check for this case and just throw some exception. Is it okay or you have other solution?

@mbait
Copy link
Author

mbait commented Jan 16, 2019

I don't know the essence of the BitTorrent protocol so I may be wrong, but from what I've already learnt it seems that BT should have no problem handling empty files: the path is present and SHA1 still cab be computed). In my application I worked around this issue even before reporting, so it's up to you whether to close it or to leave for further investigation, I just wanted to share because I also contribute to FOSS as a developer and know how important user reports can be. And, by the way, thank you for looking into this!

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