Hide field names of empty fields

https://atlas.torproject.org/#details/3CA834833A7D8C7A3473BA21A4588EBCE1281AFC lists "reject 1-65535" under the ipv4 exit policy summary (fine), but then

accept 213.0.0.0/8:8333
accept 213.0.0.0/8:443
accept 213.0.0.0/8:6667
reject *:*

under the ipv6 exit policy summary.

Oh wait, that's under the "exit policy", and there's a stray line "ipv6 exit policy summary" with nothing under it?

Maybe it shouldn't list an ipv6 exit policy summary if it isn't planning to list an ipv6 exit policy summary? :)

added component::metrics/relay search owner::irl priority::medium resolution::fixed severity::normal status::closed type::defect labels

Trac:

I looked into this and found that it's just a presentation problem. The question is, should field names be displayed if field values are empty? And if the answer is yes, should there be as much as empty space as a possible field value would have required? I don't know the answer and will leave that to phw.

The relay above is not around anymore, so I'm adding a new relay as example:

https://atlas.torproject.org/#details/EB1668E7867F172C1B82EDBB8A2F49369523C790

Also, here's a screenshot of the Atlas page. Consider "Dir Address", "IPv6 Exit Policy Summary", and "Descriptor Published" as field names without field values:

This issue is not limited to exit policies, so I'm updating the ticket summary accordingly.

Trac:
Reviewer: N/A to N/A
Severity: N/A to Normal
Summary: atlas mistakenly lists exit policy lines under "ipv6 exit policy" to Hide field names of empty fields
Sponsor: N/A to N/A

Trac:
Username: RaBe
Owner: phw to RaBe
Status: new to assigned

The issue of the empty IPv6 exit policy summary was fixed in #14328 (moved) (see https://atlas.torproject.org/#details/5CECC5C30ACC4B3DE462792323967087CC53D947 for example). This ticket would be a good place to look for the same issue in other fields.

I added alternate values for the fields "Contact", "Dir Address", (both) "Family Members" and "Descriptor Published" when otherwise they would be empty. This patch expects #20382 (moved) being already merged.

https://github.com/RaphaelBergmann/atlas/commit/140b66694b5e47478a91e8c625f2298571e442d6

Trac:
Username: RaBe
Owner: RaBe to irl

Trac:
Username: RaBe
Status: assigned to needs_review

RaBe: and for the bridge template? (:

There's something about the capitalisation and the full stop that makes me not like it. This could be a personal thing. I think the full stop is the most objectional part and I'd be happier without that, but I'll let you choose whether or not to capitalise the Nones.

Trac:
Status: needs_review to needs_revision

I copied the full stop and the capitalisation from an existing "None defined.", but I changed that one as well as my additions and now even included the bridge template :)

https://github.com/RaphaelBergmann/atlas/commit/247f40dbc55c697e4731574c4907dc59965c38aa

Trac:
Username: RaBe
Status: needs_revision to needs_review

Had to rebase, but merged. Thanks. (:

Trac:
Resolution: N/A to fixed
Status: needs_review to closed

I find "Published: Never" confusing.

Others as well: https://lists.torproject.org/pipermail/tor-relays/2017-March/012048.html

What onionoo field is used for that?

Trac:
Resolution: fixed to N/A
Status: closed to reopened

Replying to cypherpunks:

I find "Published: Never" confusing.

Others as well: https://lists.torproject.org/pipermail/tor-relays/2017-March/012048.html

What onionoo field is used for that? This is issue is outside the scope of this ticket. I've opened #21630 (moved) to address it.

Trac:
Resolution: N/A to fixed
Status: reopened to closed

closed

mentioned in issue #20382 (moved)

mentioned in issue #20649 (moved)