[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]

Re: [tor-bugs] #7987 [Metrics Website]: Descriptor types missing network-status-microdesc-consensus-3

#7987: Descriptor types missing network-status-microdesc-consensus-3
-----------------------------+----------------------------------------------
 Reporter:  atagar           |          Owner:     
     Type:  defect           |         Status:  new
 Priority:  normal           |      Milestone:     
Component:  Metrics Website  |        Version:     
 Keywords:                   |         Parent:     
   Points:                   |   Actualpoints:     
-----------------------------+----------------------------------------------

Comment(by atagar):

 > https://metrics.torproject.org/data/certs.tar.bz2
 >
 > So, it seems they're already supported in Stem, just not using that
 specific @type annotation.

 Thanks! Added support for the annotation...

 https://gitweb.torproject.org/stem.git/commitdiff/fa6ef6bca6e703e9b69a140ec5abe4c972122872

 > We don't archive microdesc consensuses, so you won't find any files
 containing them on the metrics website. That's why they aren't listed. The
 same applies to microdescs, too.

 Hmmm. Would you mind expanding the @type annotations to include things not
 on the metrics site?

 I've been getting feedback from Aaron, and last night I overhauled stem's
 parse_file() function to make it more user friendly...

 https://stem.torproject.org/api/descriptor/descriptor.html#stem.descriptor.__init__.parse_file

 One of the changes that I made was to let users specify the
 descriptor_type and added a table of descriptor_type to class mappings.

 I decided to use our @type annotations for the argument rather than making
 up something of my own because they provide a nice, canonical way of
 specifying descriptor formats. I'd rather not need to make up additional
 descriptor_types of my own to cover microdescriptors. :)

 > A fine question. Does stem add that line to microdesc consensuses that
 it receives from Tor? What about microdescs?

 Nope. Pinged Ravi on irc to ask if he remembers where this came from.

 > If I had to guess in what order need will arise, that would be: bridge-
 pool-assignments 1.0, tordnsel 1.0, torperf 1.0, directory 1.0. But it's
 hard to guess when that will be. bridge-pool-assignments might be relevant
 soon, the others maybe not.

 Ok. Let me know if/when a need arises.

 You earlier made a list of tasks we needed to make stem the primary
 descriptor parsing library (ideally so we don't need to continue
 maintaining metrics-lib as well). Thoughts on the next step?

 https://trac.torproject.org/projects/tor/wiki/doc/stem#Projects

-- 
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/7987#comment:4>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
_______________________________________________
tor-bugs mailing list
tor-bugs@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs