{"action":"created","issue":{"url":"https://api.github.com/repos/Novik/ruTorrent/issues/1066","labels_url":"https://api.github.com/repos/Novik/ruTorrent/issues/1066/labels{/name}","comments_url":"https://api.github.com/repos/Novik/ruTorrent/issues/1066/comments","events_url":"https://api.github.com/repos/Novik/ruTorrent/issues/1066/events","html_url":"https://github.com/Novik/ruTorrent/issues/1066","id":73751735,"number":1066,"title":"first element being a zero length string (REDUX, again!)","user":{"login":"AlbeSure","id":12148598,"avatar_url":"https://avatars.githubusercontent.com/u/12148598?v=3","gravatar_id":"","url":"https://api.github.com/users/AlbeSure","html_url":"https://github.com/AlbeSure","followers_url":"https://api.github.com/users/AlbeSure/followers","following_url":"https://api.github.com/users/AlbeSure/following{/other_user}","gists_url":"https://api.github.com/users/AlbeSure/gists{/gist_id}","starred_url":"https://api.github.com/users/AlbeSure/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/AlbeSure/subscriptions","organizations_url":"https://api.github.com/users/AlbeSure/orgs","repos_url":"https://api.github.com/users/AlbeSure/repos","events_url":"https://api.github.com/users/AlbeSure/events{/privacy}","received_events_url":"https://api.github.com/users/AlbeSure/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":11,"created_at":"2015-05-06T22:11:23Z","updated_at":"2015-05-07T12:06:39Z","closed_at":null,"body":"Referencing #896, #983 and #1056 \r\n\r\n**Novik**-\r\n\r\nWhile I do certainly appreciate your taking the time to respond to my previous thread (in #1056)\r\n>> where can I find that release\r\n\r\n>Try to see to the front page of project.\r\n\r\n>> and does it include the fix to the folder function, and does that fix fully resolve the null path component issue?\r\n\r\n>Try to check.\r\n\r\n...this was really NOT the clear or direct reply that I asked for and had hoped to receive.\r\n\r\nAs you suggested, I was (of course) able to locate the most recent stable release version of ruTorrent v3.7 (Released Apr 10, 2015) from the front ruTorrent project page, available from...\r\nhttps://bintray.com/novik65/generic/ruTorrent/3.7/view\r\n\r\n...BUT there are:\r\n> No release notes available for this version yet.\r\n\r\nCertain developers (namely µTorrent and briefly Transmission, as well), IMHO, were needlessly aggressive and haphazard in their response to ruTorrent's long-standing \"NON-standards compliant\" first element being a zero length string bug [documented HERE] (https://trac.transmissionbt.com/ticket/5517), and this has created *significant* problems across the greater torrent sharing community!\r\n\r\nOf course, ruTorrent is NOT a standard program that I could just easily enough download, launch and verify functionality.  While your response DOES suggest to me that this issue has, indeed, been resolved with the recent release of ruTorrent v3.7...there's just NO WAY that I could go to my seedbox provider and ask them to implement a major upgrade (such as updating to ruTorrent v3.7) with NO GUARANTEE that doing so would resolve this now very significant issue.\r\n\r\nI do REALLY appreciate your considerable effort in developing and supporting ruTorrent (it is my preferred seedbox interface).  I have personally gone to bat in support of ruTorrent on *several* private torrent servers that I am a member of (including one prominent server that I am a \"junior moderator\" for)...and also [HERE] (https://forum.transmissionbt.com/viewtopic.php?f=2&t=16626) in the Transmission forums.\r\n\r\nWhile it will NOT solve the problem of how to best \"clean-up\" the existing \"NON-standards compliant\" .torrent files...your providing a simple, clear and direct response (both here and in your v3.7 release documentation) could be a really great starting point in speeding adoption of ruTorrent v3.7 and that would be a really great benefit to the torrent sharing community as a whole!\r\n\r\nSo, with all that having been said, I return back to my original question:\r\n\r\n**Novik**, could you please clarify if the \"first element being a zero length string\" bug has been fully resolved in the release version of ruTorrent v3.7?\r\n \r\n \r\nAgain, thank you SO MUCH for your considerable efforts in creating, developing and supporting ruTorrent!\r\n\r\nSincerely,\r\n \r\n \r\n-A.S."},"comment":{"url":"https://api.github.com/repos/Novik/ruTorrent/issues/comments/99837011","html_url":"https://github.com/Novik/ruTorrent/issues/1066#issuecomment-99837011","issue_url":"https://api.github.com/repos/Novik/ruTorrent/issues/1066","id":99837011,"user":{"login":"AlbeSure","id":12148598,"avatar_url":"https://avatars.githubusercontent.com/u/12148598?v=3","gravatar_id":"","url":"https://api.github.com/users/AlbeSure","html_url":"https://github.com/AlbeSure","followers_url":"https://api.github.com/users/AlbeSure/followers","following_url":"https://api.github.com/users/AlbeSure/following{/other_user}","gists_url":"https://api.github.com/users/AlbeSure/gists{/gist_id}","starred_url":"https://api.github.com/users/AlbeSure/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/AlbeSure/subscriptions","organizations_url":"https://api.github.com/users/AlbeSure/orgs","repos_url":"https://api.github.com/users/AlbeSure/repos","events_url":"https://api.github.com/users/AlbeSure/events{/privacy}","received_events_url":"https://api.github.com/users/AlbeSure/received_events","type":"User","site_admin":false},"created_at":"2015-05-07T12:06:39Z","updated_at":"2015-05-07T12:06:39Z","body":"**JohnFlowerful** wrote:\r\n> The torrents I tested were the ones you uploaded. The ones marked as invalid were indeed invalid. The [torrent I created] (http://puu.sh/hEyzo/e3a4cc82ae.torrent) (the one in the screenshot) worked in all clients I tested.\r\n\r\nGood to know!  I feel like I was working under the presumption that the test .torrents that you reported about in your previous post were ones that you, yourself, had originally under ruTorrent v3.7...so, I do appreciate the clarification!  (Of course, as I had earlier stated, I created those sample files under ruTorrent v3.6.)\r\n\r\n> You should really test this for yourself. It could be a works4me situation on my end, but I'm 99.5% sure that this issue has been resolved.\r\n\r\nViola!  I will say that all offending versions of µTorrent have been stricken and BANNED from my computer, however, in testing YOUR sample using Transmission v2.84 (for MacOS X), the .torrent file loads WITHOUT issue!  Granted, this a very narrow sample set...but as my results under ruTorrent v3.6 (as earlier stated) were 100% reproducible, this is compelling enough evidence for me to move forward now believing that the \"first element being a zero length string\" bug has, indeed, been resolved in ruTorrent v3.7.\r\n\r\nTHANK YOU (again) **Novik** for your hard work and dedication in creating, supporting and further developing this fine product...and to **JohnFlowerful** for *very* kindly going to the effort of helping to establish that **ruTorrent v3.7 does appear to now produce 100% \"standard-compliant\" .torrent files that load and are FULLY functional under current release versions of µTorrent and Transmission (among other popular torrent clients).**\r\n\r\nKind regards,\r\n\r\n-A.S."}}