Opened 15 years ago
Closed 15 years ago
#1042 closed Bug (fixed)
Announce allowed: Never
| Reported by: | smmalis | Owned by: | charles |
|---|---|---|---|
| Priority: | Normal | Milestone: | None Set |
| Component: | Transmission | Version: | 1.22 |
| Severity: | Normal | Keywords: | |
| Cc: |
Description
When the timer for the next manual announce reaches zero, instead of saying something like: Manual Announce allowed now, it says never.
Change History (6)
comment:1 Changed 15 years ago by smmalis
- Version changed from 1.22 to 1.22+
comment:2 Changed 15 years ago by charles
- Milestone changed from None Set to 1.30
- Status changed from new to assigned
comment:3 Changed 15 years ago by charles
- Resolution set to fixed
- Status changed from assigned to closed
comment:4 Changed 15 years ago by smmalis
- Milestone changed from 1.30 to None Set
- Resolution fixed deleted
- Status changed from closed to reopened
- Summary changed from Manual Announce allowed when Never to Announce allowed: Never
Just noticed this applies to regular announce as well.
comment:5 Changed 15 years ago by charles
- Component changed from GTK+ Client to Transmission
- Version changed from 1.22+ to 1.22
The meaning of tr_stat.nextScrapeTime, tr_Stat.nextAnnounceTime, and tr_stat.manualAnnounceTime have all changed slightly:
A value of 1 now means that the scrape or announce is in progress, so we won't know until the tracker responds when the next scrape or announce is allowed. This is also documented in transmission.h.
The gtk+ client displays this '1' as "In progress" in the inspector. You might want to update the mac client to do this too. Either way, feel free to close this ticket when you're done with it.
comment:6 Changed 15 years ago by livings124
- Resolution set to fixed
- Status changed from reopened to closed
[6325] implements this in the Mac client.
fixed in r6229