If one tracker is connected successfully, then do not display timed out/failed ones

[airisama019]

this message is displayed

but here on the details a few trackers were successful

is this intentional or what

[kannibalox]

Currently the logic is "last tracker result wins", so if one tracker succeeds quickly, but the other takes a while to time out, you'll get an error message. I'm not sure how intentional that is, but my personal opinion is that it's the least worst option. rTorrent has only one line to convey error information in the TUI, with no way for it to know which failures you care about and which you don't.

If you want to disable the broken tracker, you can toggle it in the detail view with *.

[rakshasa]

It's the easiest to implement, and not big enough an issue that I've felt the need to improve the UI.

[jgiszczak]

Can the tracker error include the URL with the error? There are still many broken trackers in the world which fail NAT traversal, leading to multiple failures per torrent. It would be nice to see up front which tracker to disable when there's a persistent error visible in the UI, rather than having to carefully inspect the tracker list.

[kannibalox]

It's possible to just script the whole affair, e.g. here's a basic python script using pyrosimple that disables all trackers that have only had failures:

import pyrosimple

proxy = pyrosimple.connect().open()
resp = proxy.d.multicall2(
    "",
    "main",
    "d.hash=",
    "t.multicall=,t.success_counter=,t.failed_counter=,t.is_enabled=",
)
for r in resp:
    rhash, rtracker_data = r
    for tindex, tdata in enumerate(rtracker_data):
        success, failed, enabled = tdata
        if enabled == 1 and success == 0 and failed > 0:
            proxy.t.disable(f"{rhash}:t{tindex}")

[jgiszczak]

That script is so useful it should be added to pyrosimple's docs/examples.