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
first element being a zero length string #983
Comments
Fragment from valid torrent: Do you see difference? |
I'm trying to resolve an issue with ruTorrent and transmission. currently the transmission project receives somewhat frequent complaints that transmission rejects torrents created by ruTorrent if the "first element being a zero length string". Where the actual problem resides? It's my personal opinion the the responsibility resides with transmission and not with ruTorrent . I'm trying to become informed on the current state of ruTorrent concerning torrents with "first element being a zero length string" not suggesting a particular change but just the current status. No matter what, transmission (I believe) should accept new and old torrents from ruTorrent whether or not the "first element being a zero length string". |
This is, of course, a ruTorrent error (i.e. an error in the PHP class of Adrien), but it can't be fixed by such way, and yes, function |
Referencing #896
The fix for closed #896 seems incomplete.
static private function encode_string
remains in need of patch (per closed #896). Please correct me if I'm in error.I'm seeing below as not patched in Torrent.php
re: #896
I don't see where this particular issue was fixed in the code and newly created torrents can still be created with the first element being a zero length string.
The text was updated successfully, but these errors were encountered: