Trac issueshttps://gitlab.torproject.org/legacy/trac/-/issues2012-12-03T12:22:36Zhttps://gitlab.torproject.org/legacy/trac/-/issues/3708Fix "None" entries in relay list2012-12-03T12:22:36ZKarsten LoesingFix "None" entries in relay listWendy reports:
> A minor bug: attempting to sort the list by Bandwidth (desc) shows "None
> KB/s" at the top of the list, and "0 KB/s" at the bottom, so I don't see
> a way to show the highest bw nodes at the top. Where does "None" come...Wendy reports:
> A minor bug: attempting to sort the list by Bandwidth (desc) shows "None
> KB/s" at the top of the list, and "0 KB/s" at the bottom, so I don't see
> a way to show the highest bw nodes at the top. Where does "None" come
> from? Uptime also has both "None d" and "0 d."
I saw this problem, too, but now it's gone. I could imagine it has to do with the database schema being populated more. Any idea where the "None" values come from?https://gitlab.torproject.org/legacy/trac/-/issues/3707Remove depency on metrics-web's foreignkey branch2011-08-30T15:14:17ZKarsten LoesingRemove depency on metrics-web's foreignkey branchThe foreignkey branch of metrics-web introduced a few database schema changes to establish a foreign key relationship between statusentry and descriptor. This was necessary in order to please Django's database mapper. However, the late...The foreignkey branch of metrics-web introduced a few database schema changes to establish a foreign key relationship between statusentry and descriptor. This was necessary in order to please Django's database mapper. However, the latest TorStatus version uses its own tables which don't require the foreignkey changes anymore. Once we're really sure we don't need the foreignkey branch anymore (Jeremy, Vlad, Diego?), we should remove the parts in the README saying we need it.https://gitlab.torproject.org/legacy/trac/-/issues/1602TorStatus should use Tordnsel instead of its own2011-05-18T15:23:19ZAndrew LewmanTorStatus should use Tordnsel instead of its ownI think torstatus still uses its own "tor check" variant. We should make it use the tordnsel instead (e.g. via fetching the list of current IP addresses from the bulk exitlist, and comparing locally).I think torstatus still uses its own "tor check" variant. We should make it use the tordnsel instead (e.g. via fetching the list of current IP addresses from the bulk exitlist, and comparing locally).Karsten LoesingKarsten Loesinghttps://gitlab.torproject.org/legacy/trac/-/issues/1601Torstatus's relay listings should look in extrainfo descriptors.2012-03-10T02:58:31ZAndrew LewmanTorstatus's relay listings should look in extrainfo descriptors.Torstatus's relay listings should look in extrainfo descriptors and figure out the average actual bandwidth used by the relay. That's the main bandwidth number it should show when ranking and sorting the relays. Maybe the best way is to ...Torstatus's relay listings should look in extrainfo descriptors and figure out the average actual bandwidth used by the relay. That's the main bandwidth number it should show when ranking and sorting the relays. Maybe the best way is to add another column which just shows a number for the bandwidth the relay is advertising.Andrew LewmanAndrew Lewman