Add recommended_version parameter

With #21427 (moved) we got the version parameter which allows us to search for relays that use a version that also start with the given parameter.

A somewhat obvious use case is:

"Give me all relays with contact ... which run a version that is not recommended"

For this use-case we would need the recommended_version parameter that filters entries based on the recommended_version boolean field.

changed milestone to %Onionoo-1.8.0

added component::metrics/onionoo metrics-2017 milestone::Onionoo-1.8.0 owner::metrics-team priority::medium resolution::fixed severity::normal status::closed type::enhancement labels

Sounds like a good idea to me and shouldn't be terribly hard to implement.

Capitalize summary.

Trac:
Summary: add recommended_version parameter to Add recommended_version parameter

Trac:
Keywords: N/A deleted, metrics-2018 added

Trac:
Keywords: metrics-2018 deleted, metrics-2017 added

It was indeed not terribly hard to implement. My branch task-23544 contains an implementation that needs more review (than self review) and more testing.

But before we merge this, let's decide what to do with #23962 (moved). If we decide to include bridges in the "version" parameter, we should also include them in the "recommended_version" parameter. If we decide against it, we can move forward with this ticket by reviewing and merging my branch. But let's not do that if we later decide to change the "version" parameter, because then we'll have to do the same with the "recommended_version" parameter.

Not setting to needs_review yet.

Suggested specification for the relays-only parameter:

"Return only relays running a Tor software version that is recommended (parameter value true) or not recommended by the directory authorities (parameter value false). Relays are not contained in either result, if the version they are running is not known. Bridges are not contained in the result, regardless of which Tor version they are running. Parameter values are case-insensitive."

(I worked on all currently open (recommended) version related Onionoo tickets including this one: #22488 (moved), #23962 (moved), #21827 (moved), and #23544 (moved).)

After working on #23962 (moved) today I revised my branch above to also include bridges in the "recommended_version" parameter.

Please review the fourth commit 11e5bbd in my tasks-22488-23962-21827-23544 branch together with specification changes in commit 75c7626 in my corresponding metrics-web branch.

Trac:
Status: new to needs_review

Ready to go (cf. comments on #22488 (moved), #23962 (moved), #21827 (moved)).

(The review of of commits based on each other in one branch distributed across several tickets, is a very cumbersome review situation. If commits are as tightly connected as they are here they shouldn't be distributed on different tickets. As soon as the connection becomes apparent the tasks should be merged. The redundancy also becomes visible in the very similar ready-for-review comments and replies.)

Trac:
Status: needs_review to merge_ready

Replying to iwakeh:

Ready to go (cf. comments on #22488 (moved), #23962 (moved), #21827 (moved)).

Great, thanks for checking! Merged. Closing.

(The review of of commits based on each other in one branch distributed across several tickets, is a very cumbersome review situation. If commits are as tightly connected as they are here they shouldn't be distributed on different tickets. As soon as the connection becomes apparent the tasks should be merged. The redundancy also becomes visible in the very similar ready-for-review comments and replies.)

True. I guess next time we could merge the tickets first and then do the reviewing part there.

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

This will be part of the next release.

Trac:
Milestone: N/A to Onionoo-1.8.0

closed

mentioned in issue #23962 (moved)