Several known bugs

Some of these are older, but results in tickets (patch planned), but due to ruTorrent + rTorrent update of yesterday there is several new ones. Only a small number of servers have been updated to new ruTorrent + rTorrent.  We are working on all of these, but fix(es) cannot be done per user, or within minutes, but takes development effort. Time for this is scheduled for the upcoming week.

rTorrent + ruTorrent is by far superior software for this usage type however, but maintenance hurdles are painstaking, and upgrades on our scale are a big hurdle, not only because usually broken backwards support but also due to introduction of plethora of new bugs.

  • Browser cache has to be cleared manually due to updated JS in some cases
  • Torrent creation from ruTorrent is broken for unknown reason
  • Remove + Delete on ruTorrent doesn't work in all cases
  • Traffic plugin is broken for some users, but not all
  • ajaXplorer data deletion results in "Permission denied" in most cases
  • Quota display plugin broken due to new ruTorrent
All the ruTorrent errors are cause of upgrade breaking things (just like rTorrent updates break it's config so that rTorrent wont' even launch). They have changed things around in the core of ruTorrent which results these not working.

In details:
Creating torrents plugin: Even the old version doesn't work on the new ruTorrent. No errors given, when it does something it results in corrupted torrent. No understandable error messages are given. Defaults reportedly worked on earlier version.

Quota plugin: This is the same as before, no changes whatsoever done: Some JS function has been broken on new ruTorrent release.

Remove + Delete: No error messages, no explanation or anything. Simply broken, does nothing.

Browser cache: This would be simple solution with adding to HTML link clauses at the end of url something along: ?version=RUTORRENT_VERSION, but as the URLs are the same, browsers cache the JS files so some have to flush their cache manually.

Traffic plugin: Apparently simply does not save data for some users, but for others work. No error messages.

ajaXplorer: This is older bug (only one on the list here), and deeper rooted. Fix is in the works, but it is quite an big update.


ruTorrent doesn't create human readable (easily at least) error messages, but big unorganized and cluttered XML dumps, so reading that error log is very hard without doing it programmatically.

It does surprise us how many things got broken due to the ruTorrent upgrade, and which was not noticed on testing.

This the reason upgrades are not done as soon as released, as in general rTorrent + ruTorrent stack is maintained in a way which tends to break backwards compatibility, and other things without any obvious, logical reason. in case of rTorrent this is "just because we can break things", every single time configuration has been changed so that rTorrent fails to start because "unknown parameters", instead of giving a warning. Just as an example why it takes quite a bit of time to do these upgrades.



Sunday, February 5, 2012

« Back