Opened 8 years ago

Closed 6 years ago

#1239 closed bug (Fixed)

"Torrent not registered" not counted in Tracker Error status

Reported by: TEMHOTA Owned by: Cas
Priority: minor Milestone: 1.3.3
Component: Core Version: 1.3.2
Keywords: Cc:

Description

Why torrents with error (server report failure reason: "Not found" or "Torrent not registerd") never show in Error queue ?

Attachments (1)

deluge-screenshot.png (51.5 KB) - added by TEMHOTA 8 years ago.

Download all attachments as: .zip

Change History (11)

comment:1 Changed 8 years ago by andar

  • Resolution set to wontfix
  • Status changed from new to closed

They are tracker errors which aren't considered a fatal torrent error since you can still get peers from other sources.

comment:2 Changed 8 years ago by TEMHOTA

  • Resolution wontfix deleted
  • Status changed from closed to reopened
  • Type changed from defect to feature-request

What about private torrents (with disabled DHT) ? Maybe create "Warnings" queue and show that torrents in it? This is really annoying check all serials torrents to see - this is right torrent file or I need re-download new from tracker.

comment:3 Changed 8 years ago by andar

  • Resolution set to wontfix
  • Status changed from reopened to closed

There is already an Error tracker filter that you can use to see what torrents have tracker errors. Does this not fill this need?

comment:4 Changed 8 years ago by TEMHOTA

  • Resolution wontfix deleted
  • Status changed from closed to reopened

Error filter not working - it always show "Error(0)". See screenshot with problem torrent.

Changed 8 years ago by TEMHOTA

comment:5 Changed 8 years ago by Cas

  • Milestone set to Future
  • Priority changed from major to minor
  • Summary changed from Processing torrent server "failure reason" reply to "Torrent not registered" not counted in Tracker Error status

comment:6 Changed 6 years ago by Cas

  • Milestone changed from Future to 1.3.3
  • Owner set to Cas
  • Status changed from reopened to accepted
  • Type changed from feature-request to bug
  • Version changed from 1.2.3 to 1.3.2

This is a translation issue between on_alert_tracker_error and filtertreeview. Should not be translating strings that are used as keys.

comment:7 Changed 6 years ago by Cas

  • Resolution set to fixed
  • Status changed from accepted to closed

Fixed in 1.3-stable: ff087d133

comment:8 Changed 6 years ago by abonec

My torrent site add to torrent file 3 trackers. 1 main and 2 retrackers. When torrent was updated in website first tracker raise error (like torrent not registered) and any torrent clients what i use show me (transmission, utorrent) that one of trackers send "torrent not registered" but deluge all time show "announce is OK". I don't know that torrentfile need to update and it is big problem for me.

Please add options (or default behavior) that if one of the trackers counted error status then add this torrent to error category (or how in other clients - it has red highlight).

comment:9 Changed 6 years ago by Koroboru

  • Milestone 1.3.3 deleted
  • Resolution fixed deleted
  • Status changed from closed to reopened
  • Version changed from 1.3.2 to 1.3.3

The problem still occurs (Deluge 1.3.3). May be OK status is set because only one of the trackers return 'error: torrent not registered' status. (There are two trackers in most of my torrents: main and retracker.local. The last one may be unavailable or may send OK when main tracker sends "torrent not registered" or "closed by copyright holder" or so.) So I ask for fix, I mean that these "tracker-errored" torrents should be made somehow noticeable in UI, and not only those "not registered" but also with other error replies (e.g. "closed by copyright holder") (if it is possible). May be such behaviour can be implemented via plugin...

comment:10 Changed 6 years ago by Cas

  • Milestone set to 1.3.3
  • Resolution set to fixed
  • Status changed from reopened to closed
  • Version changed from 1.3.3 to 1.3.2

Please do not add comments or reopen a ticket when it is completely different to the bug described and subsequently fixed.

You need to either create a new feature request ticket or discuss this in the forums.

Note: See TracTickets for help on using tickets.